From: "Durrant, Paul" <xadimgnik@gmail.com>
To: Bernhard Beschow <shentey@gmail.com>, qemu-devel@nongnu.org
Cc: Richard Henderson <richard.henderson@linaro.org>,
xen-devel@lists.xenproject.org, qemu-trivial@nongnu.org,
Eduardo Habkost <eduardo@habkost.net>,
Marcel Apfelbaum <marcel.apfelbaum@gmail.com>,
Stefano Stabellini <sstabellini@kernel.org>,
Paolo Bonzini <pbonzini@redhat.com>,
"Michael S. Tsirkin" <mst@redhat.com>,
Anthony Perard <anthony.perard@citrix.com>,
Paul Durrant <paul@xen.org>
Subject: Re: [PATCH 1/2] hw/i386/xen/xen-hvm: Allow for stubbing xen_set_pci_link_route()
Date: Mon, 27 Jun 2022 09:52:26 +0100 [thread overview]
Message-ID: <0044de2b-d25e-ba76-64e1-46316e786fb4@gmail.com> (raw)
In-Reply-To: <20220626094656.15673-2-shentey@gmail.com>
On 26/06/2022 10:46, Bernhard Beschow wrote:
> The only user of xen_set_pci_link_route() is
> xen_piix_pci_write_config_client() which implements PIIX-specific logic in
> the xen namespace. This makes xen-hvm depend on PIIX which could be
> avoided if xen_piix_pci_write_config_client() was implemented in PIIX. In
> order to do this, xen_set_pci_link_route() needs to be stubbable which
> this patch addresses.
>
> Signed-off-by: Bernhard Beschow <shentey@gmail.com>
Reviewed-by: Paul Durrant <paul@xen.org>
next prev parent reply other threads:[~2022-06-27 8:52 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-26 9:46 [PATCH 0/2] Decouple Xen-HVM from PIIX Bernhard Beschow
2022-06-26 9:46 ` [PATCH 1/2] hw/i386/xen/xen-hvm: Allow for stubbing xen_set_pci_link_route() Bernhard Beschow
2022-06-27 8:52 ` Durrant, Paul [this message]
2022-06-28 22:24 ` Laurent Vivier
2022-06-26 9:46 ` [PATCH 2/2] hw/i386/xen/xen-hvm: Inline xen_piix_pci_write_config_client() and remove it Bernhard Beschow
2022-06-26 12:59 ` Michael S. Tsirkin
2022-06-27 8:52 ` Durrant, Paul
2022-06-28 22:25 ` Laurent Vivier
2022-06-28 20:58 ` [PATCH 0/2] Decouple Xen-HVM from PIIX B
2022-06-28 21:09 ` Stefano Stabellini
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=0044de2b-d25e-ba76-64e1-46316e786fb4@gmail.com \
--to=xadimgnik@gmail.com \
--cc=anthony.perard@citrix.com \
--cc=eduardo@habkost.net \
--cc=marcel.apfelbaum@gmail.com \
--cc=mst@redhat.com \
--cc=paul@xen.org \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-trivial@nongnu.org \
--cc=richard.henderson@linaro.org \
--cc=shentey@gmail.com \
--cc=sstabellini@kernel.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.