From: "Michael S. Tsirkin" <mst@redhat.com>
To: "Duan, Zhenzhong" <zhenzhong.duan@intel.com>
Cc: Jason Wang <jasowang@redhat.com>,
"Liu, Yi L" <yi.l.liu@intel.com>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
"Peng, Chao P" <chao.p.peng@intel.com>,
Yu Zhang <yu.c.zhang@linux.intel.com>,
Paolo Bonzini <pbonzini@redhat.com>,
Richard Henderson <richard.henderson@linaro.org>,
Eduardo Habkost <eduardo@habkost.net>,
Marcel Apfelbaum <marcel.apfelbaum@gmail.com>
Subject: Re: [PATCH] intel_iommu: Use the latest fault reasons defined by spec
Date: Mon, 27 May 2024 02:42:45 -0400 [thread overview]
Message-ID: <20240527024200-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <SJ0PR11MB6744135D8C08CEE42460CAF792F02@SJ0PR11MB6744.namprd11.prod.outlook.com>
On Mon, May 27, 2024 at 06:04:42AM +0000, Duan, Zhenzhong wrote:
> But I'm not sure if there is a real scenario migrating to old qemu,
> why not just update qemu on destination?
Because you can not just update a huge cluster atomically.
--
MST
next prev parent reply other threads:[~2024-05-27 6:47 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-17 10:23 [PATCH] intel_iommu: Use the latest fault reasons defined by spec Zhenzhong Duan
2024-05-17 13:13 ` CLEMENT MATHIEU--DRIF
2024-05-19 5:08 ` Liu, Yi L
2024-05-19 8:21 ` CLEMENT MATHIEU--DRIF
2024-05-20 3:11 ` Duan, Zhenzhong
2024-05-20 0:43 ` Jason Wang
2024-05-20 3:41 ` Duan, Zhenzhong
2024-05-20 4:15 ` Liu, Yi L
2024-05-20 7:55 ` Duan, Zhenzhong
2024-05-21 2:48 ` Jason Wang
2024-05-21 10:25 ` Duan, Zhenzhong
2024-05-22 8:12 ` Jason Wang
2024-05-24 8:40 ` Duan, Zhenzhong
2024-05-27 3:21 ` Jason Wang
2024-05-27 6:04 ` Duan, Zhenzhong
2024-05-27 6:32 ` Yi Liu
2024-05-27 6:49 ` Michael S. Tsirkin
2024-05-27 6:42 ` Michael S. Tsirkin [this message]
2024-05-27 6:44 ` Duan, Zhenzhong
2024-05-27 6:50 ` Michael S. Tsirkin
2024-05-28 3:03 ` Jason Wang
2024-07-02 8:42 ` Yi Liu
2024-07-17 3:30 ` Duan, Zhenzhong
2024-07-17 3:53 ` Jason Wang
2024-07-17 6:04 ` Michael S. Tsirkin
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=20240527024200-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=chao.p.peng@intel.com \
--cc=eduardo@habkost.net \
--cc=jasowang@redhat.com \
--cc=marcel.apfelbaum@gmail.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=richard.henderson@linaro.org \
--cc=yi.l.liu@intel.com \
--cc=yu.c.zhang@linux.intel.com \
--cc=zhenzhong.duan@intel.com \
/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.