From: Anthony PERARD via <qemu-devel@nongnu.org>
To: <qemu-devel@nongnu.org>
Cc: Peter Maydell <peter.maydell@linaro.org>,
Anthony PERARD <anthony.perard@citrix.com>
Subject: [PULL 0/2] Xen queue
Date: Thu, 27 Jan 2022 15:42:44 +0000 [thread overview]
Message-ID: <20220127154246.6281-1-anthony.perard@citrix.com> (raw)
The following changes since commit 48302d4eb628ff0bea4d7e92cbf6b726410eb4c3:
Merge remote-tracking branch 'remotes/dgilbert-gitlab/tags/pull-virtiofs-20220126' into staging (2022-01-26 10:59:50 +0000)
are available in the Git repository at:
https://xenbits.xen.org/git-http/people/aperard/qemu-dm.git tags/pull-xen-20220127
for you to fetch changes up to a021a2dd8b790437d27db95774969349632f856a:
xen-mapcache: Avoid entry->lock overflow (2022-01-27 15:14:21 +0000)
----------------------------------------------------------------
Xen patches
- bug fixes for mapcache and ioreq handling
----------------------------------------------------------------
Jason Andryuk (1):
xen-hvm: Allow disabling buffer_io_timer
Ross Lagerwall (1):
xen-mapcache: Avoid entry->lock overflow
hw/i386/xen/xen-hvm.c | 6 ++++--
hw/i386/xen/xen-mapcache.c | 8 +++++++-
2 files changed, 11 insertions(+), 3 deletions(-)
next reply other threads:[~2022-01-27 16:55 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-27 15:42 Anthony PERARD via [this message]
2022-01-27 15:42 ` [PULL 1/2] xen-hvm: Allow disabling buffer_io_timer Anthony PERARD via
2022-01-27 15:42 ` [PULL 2/2] xen-mapcache: Avoid entry->lock overflow Anthony PERARD via
2022-01-28 14:03 ` [PULL 0/2] Xen queue Peter Maydell
-- strict thread matches above, loose matches on Subject: below --
2022-07-05 13:45 [PULL 0/2] xen queue Anthony PERARD via
2022-07-06 1:48 ` Richard Henderson
2023-03-06 14:00 Anthony PERARD via
2023-03-07 12:41 ` Peter Maydell
2023-03-24 14:56 Anthony PERARD via
2023-03-25 16:28 ` Peter Maydell
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=20220127154246.6281-1-anthony.perard@citrix.com \
--to=qemu-devel@nongnu.org \
--cc=anthony.perard@citrix.com \
--cc=peter.maydell@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).