From: Suresh Siddha <suresh.b.siddha@intel.com>
To: "Eric W. Biederman" <ebiederm@xmission.com>
Cc: Avi Kivity <avi@redhat.com>, Gleb Natapov <gleb@redhat.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Sheng Yang <sheng@linux.intel.com>,
"kvm@vger.kernel.org" <kvm@vger.kernel.org>,
"garyhade@us.ibm.com" <garyhade@us.ibm.com>
Subject: Re: [PATCH v3] enable x2APIC without interrupt remapping under KVM
Date: Tue, 07 Jul 2009 09:14:40 -0700 [thread overview]
Message-ID: <1246983280.27006.10707.camel@localhost.localdomain> (raw)
In-Reply-To: <m1d48kndje.fsf@fess.ebiederm.org>
On Wed, 2009-07-01 at 17:17 -0700, Eric W. Biederman wrote:
> Suresh Siddha <suresh.b.siddha@intel.com> writes:
> > Among number of experiments you have tried in the past to fix this, have
> > you tried the experiment of explicitly clearing the remoteIRR by
> > changing the trigger mode to edge and then back to level.
> >
> > Is there a problem with this?
>
> The problem I had wasn't remoteIRR getting stuck, but the symptoms
> were largely the same. I did try changing the trigger mode to edge
> and back and that did not unstick the ioapic in all cases.
>
I did some experiments locally here yesterday and on my old ICH5 based
system, I couldn't reset the remoteIRR by changing the trigger mode to
edge and then back to level.
However what worked was an explicit eoi to the io-apic using the
respective vector.
I guess we need to try both the things based on perhaps io-apic version
etc.
But what I am nervous about is, did you try both these things aswell and
still saw stuck interrupts?
I will cleanup my code and post it, so that we can try on different
systems. If this still doesn't work on certain HW platforms, atleast our
experiments of what works and what doesn't work and on what platforms
will be documented on the web.
thanks,
suresh
next prev parent reply other threads:[~2009-07-07 16:17 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-29 13:29 [PATCH v3] enable x2APIC without interrupt remapping under KVM Gleb Natapov
2009-06-29 14:58 ` Suresh Siddha
2009-06-29 15:10 ` Gleb Natapov
2009-06-29 15:15 ` Suresh Siddha
2009-06-29 15:45 ` Gleb Natapov
2009-06-30 9:24 ` Eric W. Biederman
2009-06-30 9:26 ` Gleb Natapov
2009-06-30 16:44 ` Eric W. Biederman
2009-06-30 17:12 ` Avi Kivity
2009-06-30 19:08 ` Eric W. Biederman
2009-06-30 19:16 ` Avi Kivity
2009-06-30 19:36 ` Eric W. Biederman
2009-07-01 8:30 ` Avi Kivity
2009-07-01 13:31 ` Eric W. Biederman
2009-07-01 22:53 ` Suresh Siddha
2009-07-02 0:17 ` Eric W. Biederman
2009-07-07 16:14 ` Suresh Siddha [this message]
2009-07-10 20:29 ` Eric W. Biederman
2009-06-30 19:03 ` Gleb Natapov
2009-06-30 19:43 ` Eric W. Biederman
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=1246983280.27006.10707.camel@localhost.localdomain \
--to=suresh.b.siddha@intel.com \
--cc=avi@redhat.com \
--cc=ebiederm@xmission.com \
--cc=garyhade@us.ibm.com \
--cc=gleb@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sheng@linux.intel.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