From: Sean Christopherson <seanjc@google.com>
To: Michal Luczaj <mhal@rbox.co>
Cc: kvm@vger.kernel.org, pbonzini@redhat.com
Subject: Re: [PATCH 0/3] KVM: x86/emulator: Segment load fixes
Date: Thu, 26 Jan 2023 17:33:53 +0000 [thread overview]
Message-ID: <Y9K5gahXK4kWdton@google.com> (raw)
In-Reply-To: <20230126013405.2967156-1-mhal@rbox.co>
On Thu, Jan 26, 2023, Michal Luczaj wrote:
> Two small fixes for __load_segment_descriptor(), along with a KUT
> x86/emulator test.
>
> And a question to maintainers: is it ok to send patches for two repos in
> one series?
No, in the future please send two separate series (no need to do so for this case).
Us humans can easily figure out what's going on, but b4[*] gets confused, e.g.
`b4 am` will fail.
What I usually do to connect the KVM-unit-test change to the kernel/KVM change is
to post the kernel patches first, and then update the KVM-unit-test patch(es) to
provide the lore link to the kernel patches.
Thanks for asking, and a _huge_ thanks for writing tests!
[*] git://git.kernel.org/pub/scm/utils/b4/b4.git
next prev parent reply other threads:[~2023-01-26 17:34 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-26 1:34 [PATCH 0/3] KVM: x86/emulator: Segment load fixes Michal Luczaj
2023-01-26 1:34 ` [PATCH 1/3] KVM: x86/emulator: Fix segment load privilege level validation Michal Luczaj
2023-01-26 18:07 ` Paolo Bonzini
2023-01-26 1:34 ` [PATCH 2/3] KVM: x86/emulator: Fix comment in __load_segment_descriptor() Michal Luczaj
2023-01-26 18:07 ` Paolo Bonzini
2023-01-26 1:34 ` [kvm-unit-tests PATCH 3/3] x86: Test CPL=3 DS/ES/FS/GS RPL=DPL=0 segment descriptor load Michal Luczaj
2023-01-26 17:33 ` Sean Christopherson [this message]
2023-01-26 22:04 ` [PATCH 0/3] KVM: x86/emulator: Segment load fixes Michal Luczaj
2023-03-27 18:08 ` Michal Luczaj
2023-03-28 4:28 ` Sean Christopherson
2023-02-04 0:31 ` Sean Christopherson
2023-04-05 23:00 ` Sean Christopherson
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=Y9K5gahXK4kWdton@google.com \
--to=seanjc@google.com \
--cc=kvm@vger.kernel.org \
--cc=mhal@rbox.co \
--cc=pbonzini@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox