From: David Woodhouse <dwmw2@infradead.org>
To: Sean Christopherson <seanjc@google.com>
Cc: kvm <kvm@vger.kernel.org>, Paul Durrant <paul@xen.org>,
Paolo Bonzini <pbonzini@redhat.com>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
Dave Hansen <dave.hansen@linux.intel.com>,
x86@kernel.org, "H. Peter Anvin" <hpa@zytor.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] KVM: x86: Use fast path for Xen timer delivery
Date: Tue, 03 Oct 2023 18:18:38 +0100 [thread overview]
Message-ID: <6f4ada849ece727cc18a4073e1d2d568dfd8cf53.camel@infradead.org> (raw)
In-Reply-To: <ZRw9gstj8TWiiBvd@google.com>
[-- Attachment #1: Type: text/plain, Size: 503 bytes --]
On Tue, 2023-10-03 at 09:12 -0700, Sean Christopherson wrote:
>
> Holler if you plan on sending a v4 with the comment. I'm a-ok applying v3 with a
> massaged changelog to fold in the gist of the comment.
Yes please. I think you have a far better understanding of precisely
what it is that you're looking for in said comment.
I'm all for good comments, but on this occasion it seems I can't see
the wood for the trees, and I can't quite work out what it is that's
non-obvious.
Thanks!
[-- Attachment #2: smime.p7s --]
[-- Type: application/pkcs7-signature, Size: 5965 bytes --]
prev parent reply other threads:[~2023-10-03 17:18 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-29 11:36 David Woodhouse
2023-09-29 13:26 ` Durrant, Paul
2023-09-29 15:16 ` Sean Christopherson
2023-09-29 21:25 ` David Woodhouse
2023-10-02 17:41 ` Sean Christopherson
2023-10-02 18:09 ` David Woodhouse
2023-10-02 18:45 ` Sean Christopherson
2023-10-02 19:33 ` David Woodhouse
2023-10-03 16:12 ` Sean Christopherson
2023-10-03 17:18 ` David Woodhouse [this message]
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=6f4ada849ece727cc18a4073e1d2d568dfd8cf53.camel@infradead.org \
--to=dwmw2@infradead.org \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=paul@xen.org \
--cc=pbonzini@redhat.com \
--cc=seanjc@google.com \
--cc=tglx@linutronix.de \
--cc=x86@kernel.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
all inboxes | Powered by JetHome®