From: Steven Rostedt <rostedt@goodmis.org>
To: Markus Armbruster <armbru@redhat.com>
Cc: linux-input@atrey.karlin.mff.cuni.cz,
linux-kernel@vger.kernel.org,
virtualization@lists.linux-foundation.org,
Dmitry Torokhov <dtor@mail.ru>,
akpm@linux-foundation.org
Subject: Re: [PATCH] input: Fix interrupt enable in i8042_ctr when enabling interrupt fails
Date: Mon, 10 Sep 2007 08:59:11 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.4.58.0709100853340.24030@gandalf.stny.rr.com> (raw)
In-Reply-To: <877imy7kw1.fsf@pike.pond.sub.org>
--
On Mon, 10 Sep 2007, Markus Armbruster wrote:
>
> I believe this possible, but unlikely (perhaps not so unlikely on
> virtual machines). Scenarios involve enable succeeding the first
> time, failing the second time, and succeeding the third time. I can
> provide details, but the point I'd like to make is not that this is
> broken (although it is, strictly speaking), but that it is not
> obviously correct where it easily could be: just clear the interrupt
> enable bits when writing them to the hardware failed, like the old
> code did.
>
I also want to stress that this is more of a clean up for "technically
correct" code than a bug fix. This bug probably would never happen on
baremetal unless it was running on broken hardware.
BUT!!!
With more and more systems going to a virtual environment, having a bug or
some other anomaly can trigger the error that this patch prevents. The
patch will also trigger a print in the case of running on a buggy virtual
machine, which would help out the developers of that virtual machine to
fix their code.
Please apply.
-- Steve
next prev parent reply other threads:[~2007-09-10 13:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-10 12:41 Markus Armbruster
2007-09-10 12:59 ` Steven Rostedt [this message]
2007-09-10 13:14 ` Dmitry Torokhov
-- strict thread matches above, loose matches on Subject: below --
2007-07-13 13:50 Markus Armbruster
2007-07-31 12:56 ` Steven Rostedt
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=Pine.LNX.4.58.0709100853340.24030@gandalf.stny.rr.com \
--to=rostedt@goodmis.org \
--cc=akpm@linux-foundation.org \
--cc=armbru@redhat.com \
--cc=dtor@mail.ru \
--cc=linux-input@atrey.karlin.mff.cuni.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=virtualization@lists.linux-foundation.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
all inboxes | Powered by JetHome®