On 05/06/2010 03:25 PM, Gleb Natapov wrote:
We can expect that from a developer or a user subscribed to kvm@.
But what about some random user running virt-manager?
What virt-manager would do about such error?
Call up abrt.
True. But the same problem exists with cpl>0 #UD. It may be a
critical driver in userspace (say, video driver).
Also need to think consider nested kernels (which are userspace for
this purpose).
Ugh, we can check if vcpu is in nested mode.
And do what? Inject #UD to the guest? Or force some vmexit?
How about default to unconditional #UD and report, and pause if
requested (in userspace)? Usually emulation failures will be 100%
reproducible, so the user can rerun their workload.
Didn't what to involve userspace in this, but it can be done of course.
Whenever we have to make a decision, we involve userspace.
--
error compiling committee.c: too many arguments to function
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
