|
|
|
|
|
|
|
|
|
|
xen-devel
RE: [Xen-devel] address space reorganization
> > One would hope, but just because a customer has lots of
> money to spend
> > on hardware doesn't mean that he is rowing with both oars.
> This is a
> > supportability issue. The xen{source} folks would do themselves a
> > favor by trapping a guest's use of unsupported instructions and
> > logging it. That would make it easy enough to track down if a
> > customer's apps stop working when using migration.
>
> Good idea, trapping unsupported instructions and printing out
> the category the instruction belongs to (eg. SSE2) will make
> things a lot easier to track. I like this idea a lot...
Yep, although we can't trap the cpuid, we can trap the use of e.g. SSE2.
We have to be a bit careful though, to prevent DoS of the Xen console.
We'd need to rate limit such messages. Patches welcome :-)
Ian
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
<Prev in Thread] |
Current Thread |
[Next in Thread>
|
- Re: [Xen-devel] address space reorganization, (continued)
RE: [Xen-devel] address space reorganization,
Ian Pratt <=
|
Previous by Date: |
RE: [Xen-devel] [PATCH] xen, tools/python/xen: pincpu support, vcpus, add vcpu to cpu map, Ian Pratt |
Next by Date: |
Re: [Xen-devel] [PATCH] xen, tools/python/xen: pincpu support, vcpus, add vcpu to cpu map, Andrew Theurer |
Previous by Thread: |
Re: [Xen-devel] address space reorganization, Rik van Riel |
Next by Thread: |
Re: [Xen-devel] address space reorganization, Chris Wedgwood |
Indexes: |
[Date]
[Thread]
[Top]
[All Lists] |
|
|
|
|