From: Carl-Daniel Hailfinger <c-d.hailfinger.devel.2005@gmx.net>
To: Alex Williamson <alex.williamson@hp.com>
Cc: len.brown@intel.com, linux-kernel@vger.kernel.org,
acpi-devel@lists.sourceforge.net
Subject: Re: [ACPI] ACPI owner_id limit too low
Date: Thu, 08 Dec 2005 21:23:25 +0100 [thread overview]
Message-ID: <4398963D.8040207@gmx.net> (raw)
In-Reply-To: <1134066095.32040.20.camel@tdi>
Alex Williamson schrieb:
> We've found recently that it's not very hard to bump into the limit
> of the number of owner_ids that the ACPI subsystem can provide.
> [...] Doubling the limit to 64 is a sufficient short term fix
> and a fairly trivial patch, maybe even something that could go in before
> 2.6.15. Len, could we do something like the below patch to give us a
> little more reasonable limit? We could switch to a bitmap too, but
> given how close the next kernel is to release this is less impact.
> Thanks,
>
> Alex
>
>
> Signed-off-by: Alex Williamson <alex.williamson@hp.com>
> ---
>
> diff -r 03055821672a drivers/acpi/utilities/utmisc.c
> --- a/drivers/acpi/utilities/utmisc.c Mon Dec 5 01:00:10 2005
> +++ b/drivers/acpi/utilities/utmisc.c Wed Dec 7 14:55:58 2005
> @@ -84,14 +84,14 @@
>
> /* Find a free owner ID */
>
> - for (i = 0; i < 32; i++) {
> - if (!(acpi_gbl_owner_id_mask & (1 << i))) {
> + for (i = 0; i < 64; i++) {
> + if (!(acpi_gbl_owner_id_mask & (1UL << i))) {
Shouldn't this be 1ULL if you intend it to be 64 bit wide on a
32 bit arch?
Regards,
Carl-Daniel
--
http://www.hailfinger.org/
next prev parent reply other threads:[~2005-12-08 20:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-08 18:21 ACPI owner_id limit too low Alex Williamson
2005-12-08 20:23 ` Carl-Daniel Hailfinger [this message]
2005-12-08 20:36 ` [ACPI] " Alex Williamson
-- strict thread matches above, loose matches on Subject: below --
2005-12-08 22:03 Moore, Robert
2005-12-08 22:21 ` Alex Williamson
2005-12-08 23:18 Moore, Robert
2005-12-21 3:52 Brown, Len
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=4398963D.8040207@gmx.net \
--to=c-d.hailfinger.devel.2005@gmx.net \
--cc=acpi-devel@lists.sourceforge.net \
--cc=alex.williamson@hp.com \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox