From: Tyler Stachecki <stachecki.tyler@gmail.com>
To: Dongli Zhang <dongli.zhang@oracle.com>
Cc: Leonardo Bras <leobras@redhat.com>,
kvm@vger.kernel.org, seanjc@google.com, pbonzini@redhat.com,
dgilbert@redhat.com, tglx@linutronix.de, mingo@redhat.com,
dave.hansen@linux.intel.com, bp@alien8.de,
Tyler Stachecki <tstachecki@bloomberg.net>,
stable@vger.kernel.org
Subject: Re: [PATCH] x86/kvm: Account for fpstate->user_xfeatures changes
Date: Thu, 14 Sep 2023 20:58:42 -0400 [thread overview]
Message-ID: <ZQOsQjsa4bEfB28H@luigi.stachecki.net> (raw)
In-Reply-To: <93592292-ab7e-71ac-dd72-74cc76e97c74@oracle.com>
On Thu, Sep 14, 2023 at 10:05:57AM -0700, Dongli Zhang wrote:
> That is:
>
> 1. Without the commit (src and dst), something bad may happen.
>
> 2. With the commit on src, issue is fixed.
>
> 3. With the commit only dst, it is expected that issue is not fixed.
>
> Therefore, from administrator's perspective, the bugfix should always be applied
> no the source server, in order to succeed the migration.
I fully agree. Though, I think this boils down to:
The commit must be on the source or something bad may happen.
It then follows that you cannot live-migrate guests off the source to patch it
without potentially corrupting the guests currently running on that source...
Regards,
Tyler
next prev parent reply other threads:[~2023-09-15 0:58 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-14 1:00 [PATCH] x86/kvm: Account for fpstate->user_xfeatures changes Tyler Stachecki
2023-09-14 1:33 ` Tyler Stachecki
2023-09-14 7:15 ` Leonardo Bras
2023-09-14 9:11 ` Tyler Stachecki
2023-09-14 17:05 ` Dongli Zhang
2023-09-15 0:58 ` Tyler Stachecki [this message]
2023-09-15 7:41 ` Leonardo Bras
2023-09-15 12:27 ` Tyler Stachecki
2023-09-25 21:26 ` Sean Christopherson
2023-09-26 3:02 ` Tyler Stachecki
2023-09-26 16:31 ` Sean Christopherson
2023-09-26 17:31 ` Sean Christopherson
2023-09-26 19:22 ` Sean Christopherson
2023-09-26 20:27 ` Sean Christopherson
2023-09-15 7:13 ` Leonardo Bras
2023-09-15 7:11 ` Leonardo Bras
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=ZQOsQjsa4bEfB28H@luigi.stachecki.net \
--to=stachecki.tyler@gmail.com \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=dgilbert@redhat.com \
--cc=dongli.zhang@oracle.com \
--cc=kvm@vger.kernel.org \
--cc=leobras@redhat.com \
--cc=mingo@redhat.com \
--cc=pbonzini@redhat.com \
--cc=seanjc@google.com \
--cc=stable@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=tstachecki@bloomberg.net \
/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