From: Wei Liu <wl@xen.org>
To: Jan Beulich <jbeulich@suse.com>
Cc: Anthony Perard <anthony.perard@citrix.com>,
"xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>,
Ian Jackson <ian.jackson@eu.citrix.com>, Wei Liu <wl@xen.org>
Subject: Re: [Xen-devel] [PATCH 2/5] libxl/PCI: establish per-device reserved memory policy earlier
Date: Thu, 20 Feb 2020 11:38:32 +0000 [thread overview]
Message-ID: <20200220113832.jvxldbqtvrye26q7@debian> (raw)
In-Reply-To: <2124c861-bd26-1ec4-3b38-0cf24ee87c79@suse.com>
On Tue, Feb 18, 2020 at 04:46:44PM +0100, Jan Beulich wrote:
> Reserved device memory region processing as well as E820 table creation
> happen earlier than the adding of (PCI) devices, yet they consume the
> policy (e.g. to decide whether to add entries to the E820 table). But so
> far it was only at the stage of PCI device addition that the final
> policy was established (i.e. if not explicitly specified by the guest
> config file).
>
> Note that I couldn't find the domain ID to be available in
> libxl__domain_device_construct_rdm(), but observing that
> libxl__device_pci_setdefault() also doesn't use it, for the time being
> DOMID_INVALID gets passed. An obvious alternative would be to drop the
> unused parameter/argument, yet at that time the question would be
> whether to also drop other unused ones.
>
> Signed-off-by: Jan Beulich <jbeulich@suse.com>
Acked-by: Wei Liu <wl@xen.org>
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
next prev parent reply other threads:[~2020-02-20 11:38 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-18 15:44 [Xen-devel] [PATCH 0/5] libxl/PCI: reserved device memory adjustments Jan Beulich
2020-02-18 15:46 ` [Xen-devel] [PATCH 1/5] libxl/PCI: honor multiple per-device reserved memory regions Jan Beulich
2020-02-20 10:35 ` Wei Liu
2020-02-18 15:46 ` [Xen-devel] [PATCH 2/5] libxl/PCI: establish per-device reserved memory policy earlier Jan Beulich
2020-02-20 11:38 ` Wei Liu [this message]
2020-02-18 15:47 ` [Xen-devel] [PATCH 3/5] libxl/PCI: make "rdm=" parsing comply with documentation Jan Beulich
2020-02-20 11:44 ` Wei Liu
2020-02-18 15:47 ` [Xen-devel] [PATCH 4/5] libxl/PCI: pass correct "hotplug" argument to libxl__device_pci_setdefault() Jan Beulich
2020-02-20 11:41 ` Wei Liu
2020-02-18 15:47 ` [Xen-devel] [PATCH 5/5] libxl/PCI: align reserved device memory boundary for HAP guests Jan Beulich
2020-02-20 11:43 ` Wei Liu
2020-02-20 11:45 ` Jan Beulich
2020-02-20 11:48 ` Wei Liu
2020-02-20 11:45 ` [Xen-devel] [PATCH 0/5] libxl/PCI: reserved device memory adjustments Wei Liu
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=20200220113832.jvxldbqtvrye26q7@debian \
--to=wl@xen.org \
--cc=anthony.perard@citrix.com \
--cc=ian.jackson@eu.citrix.com \
--cc=jbeulich@suse.com \
--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.