From mboxrd@z Thu Jan 1 00:00:00 1970 From: =?windows-1252?Q?Roger_Pau_Monn=E9?= Subject: Re: [PATCH v6 1/2] xen/pvh: use a custom IO bitmap for PVH hardware domains Date: Fri, 15 May 2015 09:34:00 +0200 Message-ID: <5555A168.9050108@citrix.com> References: <1431356258-31269-1-git-send-email-roger.pau@citrix.com> <1431356258-31269-2-git-send-email-roger.pau@citrix.com> <55533B220200007800079F0A@mail.emea.novell.com> <5554BEFA.1020500@citrix.com> <5555AFFD020000780007A5E1@mail.emea.novell.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YtA8L-0001eH-2M for xen-devel@lists.xenproject.org; Fri, 15 May 2015 07:34:13 +0000 In-Reply-To: <5555AFFD020000780007A5E1@mail.emea.novell.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Jan Beulich Cc: Kevin Tian , SuraveeSuthikulpanit , Andrew Cooper , Eddie Dong , Aravind Gopalakrishnan , Jun Nakajima , xen-devel@lists.xenproject.org, Boris Ostrovsky List-Id: xen-devel@lists.xenproject.org El 15/05/15 a les 8.36, Jan Beulich ha escrit: >>>> On 14.05.15 at 17:27, wrote: >> El 13/05/15 a les 11.53, Jan Beulich ha escrit: >>>>>> On 11.05.15 at 16:57, wrote: >>>> --- a/xen/common/domain.c >>>> +++ b/xen/common/domain.c >>>> @@ -42,6 +42,7 @@ >>>> #include >>>> #include >>>> #include >>>> +#include >>>> >>>> /* Linux config option: propageted to domain0 */ >>>> /* xen_processor_pmbits: xen control Cx, Px, ... */ >>>> @@ -219,6 +220,7 @@ static int late_hwdom_init(struct domain *d) >>>> rangeset_swap(d->iomem_caps, dom0->iomem_caps); >>>> #ifdef CONFIG_X86 >>>> rangeset_swap(d->arch.ioport_caps, dom0->arch.ioport_caps); >>>> + setup_io_bitmap(d); >>>> #endif >>> >>> Considering that rangesets are getting swapped rather than >>> copied, I think you also need to reset Dom0's I/O bitmap here >>> to the ordinary, non-hardware domain one. >> >> Yes. Would it be fine to memset it and just call setup_io_bitmap on it >> again, or would you prefer to exchange it with the static one and free it? > > Following how the rangesets are being treated, simply swapping > the two I/O bitmaps would seem to be the right approach here. AFAICT this requires adding a new hook in hvm_function_table in order to implement setting the io bitmap for SVM and VMX. I don't have a problem with that, but it's going to need a separate patch. Roger.