xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Keir Fraser <keir.fraser@eu.citrix.com>
To: Tim Deegan <Tim.Deegan@eu.citrix.com>
Cc: "Zhang, Yang Z" <yang.z.zhang@intel.com>,
	"Zhang, Jianwu" <jianwu.zhang@intel.com>,
	"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
	"Xu, Jiajun" <jiajun.xu@intel.com>
Subject: Re: [PATCH] Re: cs:21768 causes guest spend more time on boot up
Date: Mon, 19 Jul 2010 13:24:30 +0100	[thread overview]
Message-ID: <C86A028E.1AF9E%keir.fraser@eu.citrix.com> (raw)
In-Reply-To: <20100719121905.GL13291@whitby.uk.xensource.com>

On 19/07/2010 13:19, "Tim Deegan" <Tim.Deegan@eu.citrix.com> wrote:

>>> The hang turned out to be entirely unrelated to the SMBIOS tables; the
>>> xenbus client zeroes out teh xenstore ring entirely, and it looks like
>>> newer dom0 xenbus backends can't handle that, so:
>> 
>> What would it have to do with an in-kernel driver? Doesn't the comms page
>> only get looked at by [o]xenstored? In which case we could fix them.
> 
> Ah, so it does.  I assumed it was the kernel because that's all that
> changed on my test box since I last tested this stuff.  I'm using the C
> xenstored and its code looks like it should work fine with the page
> getting zeroed under its feet.  I'll dig further.

Thanks. The revised patch might be acceptable, but if possible we're better
off relying on undocumented xenstored behaviour than domU frontend behaviour
since the former we have full control over (albeit we now have two daemons
to consider). Really nice would be some kind of explicit reset command or
protocol, but in this context since there are no watches or pending requests
or anything, I guess whacking the xenstore page is sufficient engineering
effort.

 -- Keir

  reply	other threads:[~2010-07-19 12:24 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-15  8:07 cs:21768 causes guest spend more time on boot up Zhang, Yang Z
2010-07-15  9:48 ` Tim Deegan
2010-07-15 12:22   ` Tim Deegan
2010-07-15 15:14     ` Zhang, Yang Z
2010-07-15 15:20       ` Tim Deegan
2010-07-15 15:30         ` Zhang, Yang Z
2010-07-15 15:33           ` Tim Deegan
2010-07-19 10:55             ` [PATCH] " Tim Deegan
2010-07-19 11:46               ` Keir Fraser
2010-07-19 12:19                 ` Tim Deegan
2010-07-19 12:24                   ` Keir Fraser [this message]
2010-07-19 12:30                     ` Keir Fraser
2010-07-20 10:38                   ` [PATCH] v2 (Re: cs:21768 causes guest spend more time on boot up) Tim Deegan
2010-07-20 11:16                     ` Keir Fraser
2010-07-22  9:01                       ` Zhang, Jianwu
2010-07-22 13:20                         ` Keir Fraser
2010-07-22 13:41                           ` Tim Deegan

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=C86A028E.1AF9E%keir.fraser@eu.citrix.com \
    --to=keir.fraser@eu.citrix.com \
    --cc=Tim.Deegan@eu.citrix.com \
    --cc=jiajun.xu@intel.com \
    --cc=jianwu.zhang@intel.com \
    --cc=xen-devel@lists.xensource.com \
    --cc=yang.z.zhang@intel.com \
    /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).