linux-acpi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Igor Mammedov <imammedo@redhat.com>
To: Vasilis Liaskovitis <vasilis.liaskovitis@profitbricks.com>
Cc: Toshi Kani <toshi.kani@hp.com>,
	thilo.fromm@profitbricks.com, seabios@seabios.org, rjw@sisk.pl,
	linux-acpi@vger.kernel.org
Subject: Re: [SeaBIOS] [RFC PATCH] Add _PXM to CPU objects for NUMA hot-plug
Date: Wed, 6 Nov 2013 13:54:15 +0100	[thread overview]
Message-ID: <20131106135415.1207cabb@nial.usersys.redhat.com> (raw)
In-Reply-To: <20131105102029.GA3933@shadowkeep>

On Tue, 5 Nov 2013 12:20:29 +0200
Vasilis Liaskovitis <vasilis.liaskovitis@profitbricks.com> wrote:

[...]
> > > > This issue may require a kernel fix alternatively or additionally to the seabios
> > > > fix: The kernel can save the originally parsed SRAT entry info somewhere before
> > > > it resets it at hot-remove time, and use that info on hot-plug time if the _PXM
> > > > value is missing for the hot-plugged CPU BIOS object. This way CPU hot-plug
> > > > works well against a BIOS with no CPU _PXM info.
> > 
> > To support CPU hotplug, seabios needs to implement _PXM to CPU or its
> > parent device object when the system has multiple nodes.

BTW: may we should compare linux behavior with Windows's one. usually MS implements
ACPI spec more strictly.


> ok, so no linux kernel changes are needed. Only adding PXM to seabios CPUs
> objects should be enough, which is what this RFC patch does. 
> 
> thanks,
> 
> - Vasilis
> > 
> > 
> > 
> > 
> 
> _______________________________________________
> SeaBIOS mailing list
> SeaBIOS@seabios.org
> http://www.seabios.org/mailman/listinfo/seabios


  parent reply	other threads:[~2013-11-06 12:54 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-25  9:32 [RFC PATCH][SeaBIOS] Add _PXM to CPU objects for NUMA hot-plug Vasilis Liaskovitis
2013-11-04 10:51 ` Vasilis Liaskovitis
2013-11-04 20:26   ` Toshi Kani
2013-11-05 10:20     ` Vasilis Liaskovitis
2013-11-06 12:44       ` [SeaBIOS] [RFC PATCH] " Igor Mammedov
2013-11-06 16:30         ` Toshi Kani
2013-11-06 12:54       ` Igor Mammedov [this message]
2013-11-06  2:52   ` Kevin O'Connor
2013-11-07 10:11     ` [RFC PATCH][SeaBIOS] " Vasilis Liaskovitis

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=20131106135415.1207cabb@nial.usersys.redhat.com \
    --to=imammedo@redhat.com \
    --cc=linux-acpi@vger.kernel.org \
    --cc=rjw@sisk.pl \
    --cc=seabios@seabios.org \
    --cc=thilo.fromm@profitbricks.com \
    --cc=toshi.kani@hp.com \
    --cc=vasilis.liaskovitis@profitbricks.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).