From: Matthew Garrett <mjg59@srcf.ucam.org>
To: Lee Revell <rlrevell@joe-job.com>
Cc: Greg KH <greg@kroah.com>, Alan Cox <alan@lxorguk.ukuu.org.uk>,
Daniel Drake <dsd@gentoo.org>,
akpm@osdl.org, torvalds@osdl.org, sergio@sergiomb.no-ip.org,
jeff@garzik.org, cw@f00f.org, bjorn.helgaas@hp.com,
linux-kernel@vger.kernel.org, harmon@ksu.edu,
len.brown@intel.com, vsu@altlinux.ru, liste@jordet.net
Subject: Re: [PATCH V3] VIA IRQ quirk behaviour change
Date: Sun, 10 Sep 2006 22:34:40 +0100 [thread overview]
Message-ID: <20060910213440.GA9412@srcf.ucam.org> (raw)
In-Reply-To: <1157923819.5076.185.camel@mindpipe>
On Sun, Sep 10, 2006 at 05:30:18PM -0400, Lee Revell wrote:
> Sorry, all I have is anecdotal evidence. The scope of the problem isn't
> fully known. Could be related to vendors implementing ACPI using SMM.
> Vendors are tight lipped about which hardware is affected because it
> understandably annoys users.
I don't know what you really mean by "implementing ACPI" here. Certain
queries may generate SMM traps, but I haven't seen any event driven code
paths that do[1]. If you're polling hardware you may generate some
latency, but I don't think that's any great surprise.
It would be interesting to have a test case under Linux so we could
attempt to figure out whether it's an actual problem, or just Windows
doing awkward things.
[1] outside sort of obvious stuff like ripping out a hotswap bay and
/potentially/ critical battery status to switch on a warning light, but
if you hit those situations you're probably pretty much dead anyway
--
Matthew Garrett | mjg59@srcf.ucam.org
next prev parent reply other threads:[~2006-09-10 21:34 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-07 22:33 [PATCH V3] VIA IRQ quirk behaviour change Daniel Drake
2006-09-09 14:20 ` Alan Cox
2006-09-09 14:44 ` Daniel Drake
2006-09-09 16:03 ` Alan Cox
2006-09-09 21:34 ` Daniel Drake
2006-09-10 0:31 ` Alan Cox
2006-09-10 0:21 ` Greg KH
2006-09-10 0:39 ` Chris Wedgwood
2006-09-10 4:37 ` Greg KH
2006-09-10 9:48 ` Stian Jordet
2006-09-10 15:48 ` Daniel Drake
2006-09-10 18:40 ` Lee Revell
2006-09-10 20:45 ` Matthew Garrett
2006-09-10 21:30 ` Lee Revell
2006-09-10 21:34 ` Matthew Garrett [this message]
2006-09-19 20:04 ` Lee Revell
2006-09-19 20:12 ` Matthew Garrett
2006-09-19 20:28 ` Lee Revell
2006-09-10 16:01 ` Daniel Drake
2006-09-10 16:39 ` Alan Cox
2006-09-10 16:44 ` Jeff Garzik
2006-09-10 19:06 ` Daniel Drake
2006-09-10 19:41 ` Alan Cox
2006-09-10 19:21 ` Stian Jordet
2006-09-11 15:33 ` Sergio Monteiro Basto
2006-09-11 20:16 ` Stian Jordet
2006-09-11 21:23 ` Sergio Monteiro Basto
2006-09-11 21:38 ` Stian Jordet
2006-09-12 12:37 ` Sergio Monteiro Basto
2006-09-12 21:38 ` Stian Jordet
2006-09-13 0:48 ` Sergio Monteiro Basto
2006-09-11 21:54 ` Daniel Drake
2006-09-12 6:21 ` Stian Jordet
2006-09-11 21:44 ` Daniel Drake
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=20060910213440.GA9412@srcf.ucam.org \
--to=mjg59@srcf.ucam.org \
--cc=akpm@osdl.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=bjorn.helgaas@hp.com \
--cc=cw@f00f.org \
--cc=dsd@gentoo.org \
--cc=greg@kroah.com \
--cc=harmon@ksu.edu \
--cc=jeff@garzik.org \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=liste@jordet.net \
--cc=rlrevell@joe-job.com \
--cc=sergio@sergiomb.no-ip.org \
--cc=torvalds@osdl.org \
--cc=vsu@altlinux.ru \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.