public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Ingo Molnar <mingo@elte.hu>
Cc: Rambaldi <rambaldi@xs4all.nl>,
	linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.27-rc5 xen balloon driver warnings
Date: Mon, 08 Sep 2008 11:13:52 -0700	[thread overview]
Message-ID: <48C56B60.8050604@goop.org> (raw)
In-Reply-To: <20080908175906.GA29264@elte.hu>

Ingo Molnar wrote:
> * Jeremy Fitzhardinge <jeremy@goop.org> wrote:
>
>   
>> Rambaldi wrote:
>>     
>>> Hi,
>>>
>>> when running the 2.6.27-rc5 kernel as 64 bits dumU I get the following
>>> warnings:
>>>       
>> This patch, change 167e6cf62979df03513898966f9227847d192327 in tip.git,
>> should fix this.  I'm not sure if the other sysfs changes apply to
>> mainline git or not.
>>
>> Could you try this and see how it goes?  The first chunk should be
>> sufficient to fix your problem.
>>     
>
> We could certainly propagate it to x86/urgent, if it fixes a real issue. 
> It cherry-picks just fine.
>   

The rest of that patch updates the sysfs entries in line with Andi's
changes, but I don't think they're in mainline yet.

The sysfs namespace clash means that Xen balloon and hotplug memory try
to register the same name, which is bad because one of them is going to
lose.

    J

      reply	other threads:[~2008-09-08 18:14 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-05  8:41 2.6.27-rc5 xen balloon driver warnings Rambaldi
2008-09-07 22:38 ` Jeremy Fitzhardinge
2008-09-08 15:37   ` Rambaldi
2008-09-08 16:54     ` Jeremy Fitzhardinge
2008-09-08 18:01       ` Ingo Molnar
2008-09-08 18:14         ` Jeremy Fitzhardinge
2008-09-08 18:21           ` Ingo Molnar
2008-09-08 17:59   ` Ingo Molnar
2008-09-08 18:13     ` Jeremy Fitzhardinge [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=48C56B60.8050604@goop.org \
    --to=jeremy@goop.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=rambaldi@xs4all.nl \
    /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