From: Paul Durrant <xadimgnik@gmail.com>
To: "'Jan Beulich'" <jbeulich@suse.com>
Cc: "'Ian Jackson'" <iwj@xenproject.org>,
"'Debian folks: Michael Tokarev'" <mjt@tls.msk.ru>,
"'Hans van Kranenburg'" <hans@knorrie.org>,
"'Xen upstream folks with an interest: Andrew Cooper'"
<Andrew.Cooper3@citrix.com>,
"'Roger Pau Monné'" <roger.pau@citrix.com>,
pkg-xen-devel@lists.alioth.debian.org,
xen-devel@lists.xenproject.org,
"'My Xen upstream tools co-maintainer: Wei Liu'" <wl@xen.org>
Subject: RE: qemu and Xen ABI-unstable libs
Date: Mon, 21 Sep 2020 10:50:20 +0100 [thread overview]
Message-ID: <003301d68ffc$9eaff2f0$dc0fd8d0$@xen.org> (raw)
In-Reply-To: <a034987c-3b73-cc99-fdf2-74959710b6c1@suse.com>
> -----Original Message-----
> From: Jan Beulich <jbeulich@suse.com>
> Sent: 21 September 2020 10:41
> To: paul@xen.org
> Cc: 'Ian Jackson' <iwj@xenproject.org>; 'Debian folks: Michael Tokarev' <mjt@tls.msk.ru>; 'Hans van
> Kranenburg' <hans@knorrie.org>; 'Xen upstream folks with an interest: Andrew Cooper'
> <Andrew.Cooper3@citrix.com>; 'Roger Pau Monné' <roger.pau@citrix.com>; pkg-xen-
> devel@lists.alioth.debian.org; xen-devel@lists.xenproject.org; 'My Xen upstream tools co-maintainer:
> Wei Liu' <wl@xen.org>
> Subject: Re: qemu and Xen ABI-unstable libs
>
> On 21.09.2020 09:36, Paul Durrant wrote:
> >> From: Xen-devel <xen-devel-bounces@lists.xenproject.org> On Behalf Of Ian Jackson
> >> Sent: 18 September 2020 17:39
> >>
> >> xc_domain_iomem_permission
> >> xc_domain_populate_physmap_exact
> >> xc_domain_ioport_mapping
> >> xc_domain_memory_mapping
> >>
> >> The things done by these calls in qemu should be done by the Xen
> >> toolstack (libxl), during domain creation etc., instead.
> >
> > I don't think that is practical. E.g. if a guest re-programs a PCI I/O BAR then it may necessitate
> re-calling
> > xc_domain_ioport_mapping(); the tool-stack cannot know a priori where PCI BARs will end up in guest
> port/memory space.
>
> In your reply I assume you meant just the latter two of the four?
> For these I agree, and as a result they shouldn't be domctl in
> the new model.
>
Sorry if I wasn't clear. Yes, the latter two are what I was referring to.
Paul
> Jan
next prev parent reply other threads:[~2020-09-21 9:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-18 16:39 RFC: qemu and Xen ABI-unstable libs Ian Jackson
2020-09-21 7:36 ` Paul Durrant
2020-09-21 9:40 ` Jan Beulich
2020-09-21 9:50 ` Paul Durrant [this message]
2020-09-21 10:16 ` Roger Pau Monné
2020-09-21 10:36 ` Paul Durrant
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='003301d68ffc$9eaff2f0$dc0fd8d0$@xen.org' \
--to=xadimgnik@gmail.com \
--cc=Andrew.Cooper3@citrix.com \
--cc=hans@knorrie.org \
--cc=iwj@xenproject.org \
--cc=jbeulich@suse.com \
--cc=mjt@tls.msk.ru \
--cc=paul@xen.org \
--cc=pkg-xen-devel@lists.alioth.debian.org \
--cc=roger.pau@citrix.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.