qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Philippe Mathieu-Daudé" <philmd@linaro.org>
To: David Woodhouse <dwmw2@infradead.org>, qemu-devel@nongnu.org
Cc: Paul Durrant <paul@xen.org>, Paolo Bonzini <pbonzini@redhat.com>,
	Richard Henderson <richard.henderson@linaro.org>,
	Eduardo Habkost <eduardo@habkost.net>,
	"Michael S. Tsirkin" <mst@redhat.com>,
	Marcel Apfelbaum <marcel.apfelbaum@gmail.com>,
	Marcelo Tosatti <mtosatti@redhat.com>,
	kvm@vger.kernel.org, Peter Maydell <peter.maydell@linaro.org>,
	Anthony PERARD <anthony.perard@citrix.com>
Subject: Re: [PATCH for-8.1] Misc Xen-on-KVM fixes
Date: Tue, 1 Aug 2023 23:46:05 +0200	[thread overview]
Message-ID: <07c4b978-4ad9-c9ff-38d1-d24f4c701dd6@linaro.org> (raw)
In-Reply-To: <20230801175747.145906-1-dwmw2@infradead.org>

On 1/8/23 19:57, David Woodhouse wrote:
> A few minor fixes for the Xen emulation support. One was just merged, but
> there are three outstanding.
> 
> David Woodhouse (3):
>        hw/xen: fix off-by-one in xen_evtchn_set_gsi()
>        i386/xen: consistent locking around Xen singleshot timers
>        hw/xen: prevent guest from binding loopback event channel to itself
> 
>   hw/i386/kvm/xen_evtchn.c  | 15 +++++++++++----
>   target/i386/kvm/xen-emu.c | 36 ++++++++++++++++++++++++++----------
>   2 files changed, 37 insertions(+), 14 deletions(-)

Thanks, since the series is reviewed, I'm queuing via misc-fixes.



      parent reply	other threads:[~2023-08-01 21:46 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-01 17:57 [PATCH for-8.1] Misc Xen-on-KVM fixes David Woodhouse
2023-08-01 17:57 ` [PATCH for-8.1 1/3] hw/xen: fix off-by-one in xen_evtchn_set_gsi() David Woodhouse
2023-08-01 17:57 ` [PATCH for-8.1 2/3] i386/xen: consistent locking around Xen singleshot timers David Woodhouse
2023-08-01 17:57 ` [PATCH for-8.1 3/3] hw/xen: prevent guest from binding loopback event channel to itself David Woodhouse
2023-08-01 21:46 ` Philippe Mathieu-Daudé [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=07c4b978-4ad9-c9ff-38d1-d24f4c701dd6@linaro.org \
    --to=philmd@linaro.org \
    --cc=anthony.perard@citrix.com \
    --cc=dwmw2@infradead.org \
    --cc=eduardo@habkost.net \
    --cc=kvm@vger.kernel.org \
    --cc=marcel.apfelbaum@gmail.com \
    --cc=mst@redhat.com \
    --cc=mtosatti@redhat.com \
    --cc=paul@xen.org \
    --cc=pbonzini@redhat.com \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=richard.henderson@linaro.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 NNTP newsgroup(s).