Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1649723
| From | Boris Ostrovsky <boris.ostrovsky@oracle.com> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | Re: [PATCH 05/10] paravirt: add new PARAVIRT_FULL config item |
| Date | 2017-05-24 17:50 +0200 |
| Message-ID | <tKGHU-49Y-23@gated-at.bofh.it> (permalink) |
| References | <tISk9-4bg-3@gated-at.bofh.it> <tISka-4bg-25@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
On 05/19/2017 11:47 AM, Juergen Gross wrote: > Add a new config item PARAVIRT_FULL. It will be used to guard the > pv_*_ops functions used by fully paravirtualized guests (Xen pv-guests > and lguest) only. > > Kernels not meant to support those guest types will be able to use many > operations without paravirt abstraction while still supporting all the > other paravirt features. > > For now just add the new Kconfig option and select it for XEN_PV and > LGUEST_GUEST. Add paravirt_full.c, paravirt_full.h and > paravirt_types_full.h which will contain the necessary implementation > parts of the pv guest specific paravirt functions. Is it not possible to just 'ifdef CONFIG_PARAVIT_FULL' the (ir)relevant parts of paravirt.[ch] and paravirt_types.c? Separating structures and files into pv and pvfull seems somewhat arbitrary (.flush_tlb_others in patch 8 being a good example of one type of guest deciding to use something that normally would be considered part of a pvfull-type structure). -boris
Back to linux.kernel | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
[PATCH 05/10] paravirt: add new PARAVIRT_FULL config item Juergen Gross <jgross@suse.com> - 2017-05-19 17:50 +0200
Re: [PATCH 05/10] paravirt: add new PARAVIRT_FULL config item Boris Ostrovsky <boris.ostrovsky@oracle.com> - 2017-05-24 17:50 +0200
Re: [PATCH 05/10] paravirt: add new PARAVIRT_FULL config item Juergen Gross <jgross@suse.com> - 2017-05-24 18:50 +0200
csiph-web