All of lore.kernel.org
 help / color / mirror / Atom feed
From: Anthony PERARD <anthony.perard@citrix.com>
To: Andrew Cooper <amc96@srcf.net>
Cc: Juergen Gross <jgross@suse.com>, <xen-devel@lists.xenproject.org>,
	"Ian Jackson" <iwj@xenproject.org>, Wei Liu <wl@xen.org>,
	Andrew Cooper <andrew.cooper3@citrix.com>
Subject: Re: [PATCH v3 2/2] tools: set event channel HVM parameters in libxenguest
Date: Wed, 8 Dec 2021 16:34:54 +0000	[thread overview]
Message-ID: <YbDerlN/E1wFrZKY@perard> (raw)
In-Reply-To: <4d48cc2f-bea4-c1f4-95ec-4efa6d56b661@srcf.net>

On Wed, Dec 08, 2021 at 04:02:17PM +0000, Andrew Cooper wrote:
> On 08/12/2021 15:57, Juergen Gross wrote:
> > On 08.12.21 16:54, Andrew Cooper wrote:
> >> On 08/12/2021 14:22, Juergen Gross wrote:
> >>> On 08.12.21 14:43, Andrew Cooper wrote:
> >>>> On 08/12/2021 08:47, Juergen Gross wrote:
> >>>>> The HVM parameters for pre-allocated event channels should be set in
> >>>>> libxenguest, like it is done for PV guests and for the pre-allocated
> >>>>> ring pages.
> >>>>>
> >>>>> Suggested-by: Andrew Cooper <andrew.cooper3@citrix.com>
> >>>>> Signed-off-by: Juergen Gross <jgross@suse.com>
> >>>>
> >>>> I'm not sure that we have the concept of pre-allocated ring pages.
> >>>>
> >>>> For PV, we have:
> >>>>
> >>>>       dom->console_pfn = xc_dom_alloc_page(dom, "console");
> >>>>       if ( dom->console_pfn == INVALID_PFN )
> >>>>           return -1;
> >>>>       xc_clear_domain_page(dom->xch, dom->guest_domid,
> >>>>                            xc_dom_p2m(dom, dom->console_pfn));
> >>>>
> >>>> and for HVM, we have:
> >>>>
> >>>>       dom->console_pfn = special_pfn(SPECIALPAGE_CONSOLE);
> >>>>       xc_clear_domain_page(dom->xch, dom->guest_domid,
> >>>> dom->console_pfn);
> >>>
> >>> Isn't that a pre-allocation? The PFNs are fixed at boot time of the
> >>> guest.
> >>
> >> Yeah, but "allocated in the library call we're making" is not the same
> >> as "caller has to allocate and pass details in".
> >>
> >> I would not class the frames as "pre-allocated" in this context.
> >> "allocated" sure, so perhaps "just like it is done for PV guests, and
> >> the ring pages that libxenguest allocates" ?
> >
> > Fine with me.
> >
> > Should I send another round, or can this be changed when committing?
> 
> Fixed on commit.  No need to resend just for this.
> 
> Question is whether Anthony has any view, or whether my R-by is good enough?

Patch looks good, so:
Acked-by: Anthony PERARD <anthony.perard@citrix.com>

Thanks,

-- 
Anthony PERARD


      reply	other threads:[~2021-12-08 16:35 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-08  8:47 [PATCH v3 0/2] tools/helpers: PVH xenstore-stubdom console fixes Juergen Gross
2021-12-08  8:47 ` [PATCH v3 1/2] tools/helpers: fix PVH xenstore-stubdom console parameters Juergen Gross
2021-12-08  8:47 ` [PATCH v3 2/2] tools: set event channel HVM parameters in libxenguest Juergen Gross
2021-12-08 13:43   ` Andrew Cooper
2021-12-08 14:22     ` Juergen Gross
2021-12-08 15:54       ` Andrew Cooper
2021-12-08 15:57         ` Juergen Gross
2021-12-08 16:02           ` Andrew Cooper
2021-12-08 16:34             ` Anthony PERARD [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=YbDerlN/E1wFrZKY@perard \
    --to=anthony.perard@citrix.com \
    --cc=amc96@srcf.net \
    --cc=andrew.cooper3@citrix.com \
    --cc=iwj@xenproject.org \
    --cc=jgross@suse.com \
    --cc=wl@xen.org \
    --cc=xen-devel@lists.xenproject.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.