From: Boris Ostrovsky <boris.ostrovsky@oracle.com>
To: Juergen Gross <jgross@suse.com>,
linux-kernel@vger.kernel.org, xen-devel@lists.xenproject.org
Subject: Re: [PATCH v3 3/3] xen: optimize xenbus driver for multiple concurrent xenstore accesses
Date: Tue, 7 Feb 2017 12:51:42 -0500 [thread overview]
Message-ID: <d7d62002-ef62-8496-af95-136adb73d913__44007.1572702893$1486489895$gmane$org@oracle.com> (raw)
In-Reply-To: <12bbe7e7-eea4-09d0-8282-0b04504daeb2@suse.com>
On 01/24/2017 11:23 AM, Juergen Gross wrote:
> On 24/01/17 14:47, Boris Ostrovsky wrote:
>> On 01/23/2017 01:59 PM, Boris Ostrovsky wrote:
>>> On 01/23/2017 05:09 AM, Juergen Gross wrote:
>>>> Handling of multiple concurrent Xenstore accesses through xenbus driver
>>>> either from the kernel or user land is rather lame today: xenbus is
>>>> capable to have one access active only at one point of time.
>>>>
>>>>
>>
>> This patch appears to break save/restore:
> Hmm, tried multiple times, but I can't reproduce this issue.
>
> Anything special in the setup? I tried a 64 bit pv guest and did
> "xl save".
>
> Do I have to run some load in parallel?
Any luck reproducing this? I am still failing the test on dumpdata but I
couldn't reproduce it on another system.
-boris
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next prev parent reply other threads:[~2017-02-07 17:50 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-23 10:09 [PATCH v3 0/3] xen: optimize xenbus performance Juergen Gross
2017-01-23 10:09 ` [PATCH v3 1/3] xen: clean up xenbus internal headers Juergen Gross
2017-01-23 10:09 ` Juergen Gross
2017-01-23 10:09 ` [PATCH v3 2/3] xen: modify xenstore watch event interface Juergen Gross
2017-01-23 10:09 ` Juergen Gross
2017-01-23 10:09 ` [PATCH v3 3/3] xen: optimize xenbus driver for multiple concurrent xenstore accesses Juergen Gross
2017-01-23 10:09 ` Juergen Gross
2017-01-23 18:59 ` Boris Ostrovsky
2017-01-23 18:59 ` Boris Ostrovsky
2017-01-24 13:47 ` Boris Ostrovsky
2017-01-24 16:23 ` Juergen Gross
2017-01-24 16:23 ` Juergen Gross
2017-01-24 17:17 ` Boris Ostrovsky
2017-01-24 17:17 ` Boris Ostrovsky
2017-02-07 17:51 ` Boris Ostrovsky [this message]
2017-02-07 17:51 ` Boris Ostrovsky
2017-02-07 22:39 ` Boris Ostrovsky
2017-02-07 22:39 ` Boris Ostrovsky
2017-02-08 6:21 ` Juergen Gross
2017-02-08 6:21 ` Juergen Gross
2017-01-24 13:47 ` Boris Ostrovsky
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='d7d62002-ef62-8496-af95-136adb73d913__44007.1572702893$1486489895$gmane$org@oracle.com' \
--to=boris.ostrovsky@oracle.com \
--cc=jgross@suse.com \
--cc=linux-kernel@vger.kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.