From: "Jan Beulich" <jbeulich@novell.com>
To: "Andi Kleen" <andi@firstfloor.org>,
"Robert Moore" <robert.moore@intel.com>,
"Len Brown" <lenb@kernel.org>
Cc: "Robert Gough" <robert.gough@intel.com>,
"Andrew Paprocki" <andrew@ishiboo.com>,
"Takashi Iwai" <tiwai@suse.de>,
"LKML" <linux-kernel@vger.kernel.org>
Subject: RE: Endless ACPI errors on Linus tree (5b664cb235)
Date: Wed, 23 Jul 2008 17:14:09 +0100 [thread overview]
Message-ID: <488774F1.76E4.0078.0@novell.com> (raw)
In-Reply-To: <9D39833986E69849A2A8E74C1078B6B3B68DDD@orsmsx415.amr.corp.intel.com>
>>> "Moore, Robert" <robert.moore@intel.com> 23.07.08 17:43 >>>
>Couple of thoughts.
>
>I think we must use the V2 field if it is present and the address value
>is > 32 bits.
>
>What if the V2 address is < 32 bits but does not match the V1 address?
The v2 address was used already before this patch, the patch just
(initially) tried to make things consistent to use the v2 bit width along
with the v2 address. That didn't work out. I certainly think there's room
for improvement, but perhaps (at least at present) of more academical
nature: If the v2 widths indicate a value wider than the v1 ones, then
we could still try to use the v2 field. The breakages reported so far
were only in the v2 widths being smaller than the v1 ones...
Jan
next prev parent reply other threads:[~2008-07-23 16:13 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-18 11:24 Endless ACPI errors on Linus tree (5b664cb235) Takashi Iwai
2008-07-18 11:35 ` Andi Kleen
2008-07-18 13:15 ` Takashi Iwai
2008-07-18 13:34 ` Takashi Iwai
2008-07-18 15:48 ` Takashi Iwai
2008-07-18 15:52 ` Andi Kleen
2008-07-18 15:56 ` Takashi Iwai
2008-07-18 16:16 ` Jan Beulich
2008-07-18 16:38 ` Takashi Iwai
2008-07-18 16:58 ` Andi Kleen
2008-07-19 9:23 ` Takashi Iwai
2008-07-21 8:11 ` Jan Beulich
2008-07-21 8:43 ` Andi Kleen
2008-07-23 11:27 ` Jan Beulich
2008-07-23 15:43 ` Moore, Robert
2008-07-23 16:14 ` Jan Beulich [this message]
2008-09-17 4:56 ` Andrew Paprocki
2008-09-17 6:43 ` Jan Beulich
2008-09-17 15:04 ` Andi Kleen
2008-07-18 15:52 ` Andi Kleen
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=488774F1.76E4.0078.0@novell.com \
--to=jbeulich@novell.com \
--cc=andi@firstfloor.org \
--cc=andrew@ishiboo.com \
--cc=lenb@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robert.gough@intel.com \
--cc=robert.moore@intel.com \
--cc=tiwai@suse.de \
/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