From: Bjorn Helgaas <bjorn.helgaas@hp.com>
To: Jes Sorensen <jes@trained-monkey.org>, linux-kernel@vger.kernel.org
Cc: acpi-devel@lists.sourceforge.net, jbarnes@sgi.com, steiner@sgi.com
Subject: Re: [ACPI] RFC: ACPI table overflow handling
Date: Thu, 8 Jan 2004 09:20:04 -0700 [thread overview]
Message-ID: <200401080920.04906.bjorn.helgaas@hp.com> (raw)
In-Reply-To: <16381.27904.580087.442358@gargle.gargle.HOWL>
On Thursday 08 January 2004 7:45 am, Jes Sorensen wrote:
> I could just hack the NUMA srat_num_cpus handling code to have a limit
> as IMHO it is a lot cleaner to improve the acpi_table_parse_madt() API
> by adding a max_entries argument and then have acpi_table_parse_madt
> spit out a warning if it found too many entries.
I really like this idea. I notice you didn't take the opportunity to
remove the ad hoc checking in ia64 acpi_parse_lsapic; probably that's
the next step. Also, did you consider using max_entries==0 to signify
"unlimited"? Zero seems like an otherwise useless value for max_entries
and would avoid having to choose an arbitrary limit.
next prev parent reply other threads:[~2004-01-08 16:20 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-08 14:45 Jes Sorensen
2004-01-08 16:20 ` Bjorn Helgaas [this message]
2004-01-11 11:49 ` [ACPI] " Jes Sorensen
2004-01-11 14:30 ` Jes Sorensen
2004-01-12 16:24 ` Bjorn Helgaas
2004-01-13 9:49 ` Jes Sorensen
2004-01-13 10:45 ` [patch] ACPI NUMA quiet printk and cleanup Jes Sorensen
2004-01-13 23:01 ` [ACPI] RFC: ACPI table overflow handling Bjorn Helgaas
2004-01-13 13:13 ` [patch] ia64 header cleanup Jes Sorensen
[not found] <BF1FE1855350A0479097B3A0D2A80EE001E60811@hdsmsx402.hd.intel.com>
2004-01-28 5:20 ` [ACPI] RFC: ACPI table overflow handling Len Brown
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=200401080920.04906.bjorn.helgaas@hp.com \
--to=bjorn.helgaas@hp.com \
--cc=acpi-devel@lists.sourceforge.net \
--cc=jbarnes@sgi.com \
--cc=jes@trained-monkey.org \
--cc=linux-kernel@vger.kernel.org \
--cc=steiner@sgi.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
all inboxes | Powered by JetHome®