| |
|
 |
|
 |
|
|
|
| |
|
|
xen-ia64-devel
Re: [Xen-ia64-devel] [RFC][PATCH] [RESEND] support special guest optimis
Quoting Dietmar Hahn <dietmar.hahn@xxxxxxxxxxxxxxxxxxx>:
> Am Freitag, 29. Juni 2007 schrieb Tristan Gingold:
> > > attached to this mail are 2 patches:
> > > - opt_feature_xen.patch
> > > implements the new hypercall __HYPERVISOR_opt_feature in the
> > > hypervisor. - opt_feature_linux.patch
> > > implements the usage of the hypercall.
> >
> > I think the hypercall interface is a little bit overkill but who knows
> > about the future?
> Which part do you mean with overkill?
> For the function call I used the same scheme the other hypercalls use.
> Or do you mean the structure?
To be clear: I am not opposed to your patch.
I think a simple feature bitmap would have been enough (and would have avoid
xencom mechanism).
> What I wanted to do was a common solution. All the hypervisor needs to handle
> the identity mapping insertion are the access bit of the pte and (maybe in
> the future) the protection key.
Why not.
> Ok, I can remove the key, because there is currently no guest using this. And
> we can add it, when it will be necessary - should I resend the patch without
> the key?
No need.
Tristan.
_______________________________________________
Xen-ia64-devel mailing list
Xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-ia64-devel
|
|
|
| |
|
Home