From: "Oleksii K." <oleksii.kurochko@gmail.com>
To: "Stewart Hildebrand" <stewart.hildebrand@amd.com>,
xen-devel@lists.xenproject.org,
"Roger Pau Monné" <roger.pau@citrix.com>
Cc: Jiqian Chen <Jiqian.Chen@amd.com>,
Jan Beulich <jbeulich@suse.com>,
Andrew Cooper <andrew.cooper3@citrix.com>, Wei Liu <wl@xen.org>,
George Dunlap <george.dunlap@citrix.com>,
Julien Grall <julien@xen.org>,
Stefano Stabellini <sstabellini@kernel.org>,
Anthony PERARD <anthony.perard@citrix.com>,
Juergen Gross <jgross@suse.com>,
"Daniel P . Smith" <dpsmith@apertussolutions.com>,
Huang Rui <Ray.Huang@amd.com>
Subject: Re: [XEN PATCH v7 1/5] xen/vpci: Clear all vpci status of device
Date: Thu, 16 May 2024 18:07:54 +0200 [thread overview]
Message-ID: <0bb2becc5b5d327f6b3b878b876da78034bcebd6.camel@gmail.com> (raw)
In-Reply-To: <4eab3820-d357-42cb-a367-a7a0966e7e3b@amd.com>
On Wed, 2024-05-15 at 10:27 -0400, Stewart Hildebrand wrote:
> On 4/18/24 23:53, Jiqian Chen wrote:
> > When a device has been reset on dom0 side, the vpci on Xen
> > side won't get notification, so the cached state in vpci is
> > all out of date compare with the real device state.
> > To solve that problem, add a new hypercall to clear all vpci
> > device state. When the state of device is reset on dom0 side,
> > dom0 can call this hypercall to notify vpci.
> >
> > Signed-off-by: Huang Rui <ray.huang@amd.com>
> > Signed-off-by: Jiqian Chen <Jiqian.Chen@amd.com>
> > Reviewed-by: Stewart Hildebrand <stewart.hildebrand@amd.com>
> > Reviewed-by: Stefano Stabellini <sstabellini@kernel.org>
>
> Could we consider this patch for 4.19? It's independent of the rest
> of
> this series, and it fixes a real issue observed on both Arm and x86.
> The
> Linux counterpart has already been merged in linux-next [0].
>
> [0]
> https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?h=next-20240515&id=b272722511d5e8ae580f01830687b8a6b2717f01
Sure! Fixes should be merged.
Release-acked-by: Oleksii Kurochko <oleksii.kurochko@gmail.com>
~ Oleksii
next prev parent reply other threads:[~2024-05-16 16:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-19 3:53 [RFC XEN PATCH v7 0/5] Support device passthrough when dom0 is PVH on Xen Jiqian Chen
2024-04-19 3:53 ` [XEN PATCH v7 1/5] xen/vpci: Clear all vpci status of device Jiqian Chen
2024-05-15 14:27 ` Stewart Hildebrand
2024-05-16 16:07 ` Oleksii K. [this message]
2024-04-19 3:53 ` [XEN PATCH v7 2/5] x86/pvh: Allow (un)map_pirq when dom0 is PVH Jiqian Chen
2024-04-19 3:53 ` [RFC XEN PATCH v7 3/5] x86/pvh: Add PHYSDEVOP_setup_gsi for PVH dom0 Jiqian Chen
2024-04-19 3:53 ` [RFC XEN PATCH v7 4/5] tools: Add new function to get gsi from irq Jiqian Chen
2024-04-19 3:53 ` [RFC XEN PATCH v7 5/5] domctl: Add XEN_DOMCTL_gsi_permission to grant gsi Jiqian Chen
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=0bb2becc5b5d327f6b3b878b876da78034bcebd6.camel@gmail.com \
--to=oleksii.kurochko@gmail.com \
--cc=Jiqian.Chen@amd.com \
--cc=Ray.Huang@amd.com \
--cc=andrew.cooper3@citrix.com \
--cc=anthony.perard@citrix.com \
--cc=dpsmith@apertussolutions.com \
--cc=george.dunlap@citrix.com \
--cc=jbeulich@suse.com \
--cc=jgross@suse.com \
--cc=julien@xen.org \
--cc=roger.pau@citrix.com \
--cc=sstabellini@kernel.org \
--cc=stewart.hildebrand@amd.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).