From: Olaf Hering <olaf@aepfle.de>
To: Anthony PERARD <anthony.perard@citrix.com>
Cc: xen-devel@lists.xenproject.org, "Wei Liu" <wei.liu2@citrix.com>,
"Roger Pau Monné" <roger.pau@citrix.com>
Subject: Re: [Xen-devel] [PATCH qemu-xen 4.10 & 4.11] xen_disk: Disable file locking for the PV disk backend
Date: Fri, 14 Jun 2019 15:23:03 +0200 [thread overview]
Message-ID: <20190614152303.12d95e85.olaf@aepfle.de> (raw)
In-Reply-To: <20190605105338.GH2126@perard.uk.xensource.com>
[-- Attachment #1.1: Type: text/plain, Size: 517 bytes --]
Am Wed, 5 Jun 2019 11:53:38 +0100
schrieb Anthony PERARD <anthony.perard@citrix.com>:
> Olaf, did you apply this patch and run some guest? Do they still boot?
> It doesn't matter if you can't trigger the race with or without this
> patch, I just want to know if there are any regression.
> So, may have I your "Tested-by" ? And I will try to apply it to our
> qemu-xen branches.
I can not reproduce it myself on the systems I have available.
It seems that patch went already into qemu-xen.git.
Olaf
[-- Attachment #1.2: Digitale Signatur von OpenPGP --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
[-- Attachment #2: Type: text/plain, Size: 157 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
prev parent reply other threads:[~2019-06-14 13:23 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-22 14:51 [PATCH qemu-xen 4.10 & 4.11] xen_disk: Disable file locking for the PV disk backend Anthony PERARD
2019-05-22 14:51 ` [Xen-devel] " Anthony PERARD
2019-05-22 14:54 ` Wei Liu
2019-05-22 14:54 ` [Xen-devel] " Wei Liu
2019-05-22 17:54 ` Olaf Hering
2019-05-22 17:54 ` [Xen-devel] " Olaf Hering
2019-05-23 9:41 ` Anthony PERARD
2019-05-23 9:41 ` [Xen-devel] " Anthony PERARD
2019-06-05 10:53 ` Anthony PERARD
2019-06-14 13:23 ` Olaf Hering [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=20190614152303.12d95e85.olaf@aepfle.de \
--to=olaf@aepfle.de \
--cc=anthony.perard@citrix.com \
--cc=roger.pau@citrix.com \
--cc=wei.liu2@citrix.com \
--cc=xen-devel@lists.xenproject.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).