All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gleb Natapov <gleb@redhat.com>
To: Marcelo Tosatti <mtosatti@redhat.com>
Cc: Jan Kiszka <jan.kiszka@web.de>, kvm <kvm@vger.kernel.org>
Subject: Re: [PATCH v2] KVM: x86: Remove support for reporting coalesced APIC IRQs
Date: Tue, 14 May 2013 12:10:17 +0300	[thread overview]
Message-ID: <20130514091017.GC20995@redhat.com> (raw)
In-Reply-To: <20130514013033.GA32410@amt.cnet>

On Mon, May 13, 2013 at 10:30:33PM -0300, Marcelo Tosatti wrote:
> On Thu, May 02, 2013 at 10:14:32PM -0300, Marcelo Tosatti wrote:
> > On Sun, Apr 28, 2013 at 02:00:41PM +0200, Jan Kiszka wrote:
> > > From: Jan Kiszka <jan.kiszka@siemens.com>
> > > 
> > > Since the arrival of posted interrupt support we can no longer guarantee
> > > that coalesced IRQs are always reported to the IRQ source. Moreover,
> > > accumulated APIC timer events could cause a busy loop when a VCPU should
> > > rather be halted. The consensus is to remove coalesced tracking from the
> > > LAPIC.
> > > 
> > > Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>
> > > ---
> > > 
> > > Changes in v2:
> > >  - preserve return values where we need to count to how many VCPUs an
> > >    IRQ was delivered
> > 
> > It would be best to confirm first that no guest depends on LAPIC timer
> > reinjection (rather than wait for guests to break and spend time
> > debugging). Specially since such kind of bugs are not easy to pinpoint.
> > Or if there is evidence to invalidate such reasoning, please point it
> > out.
> > 
> > Honestly i don't recall: would have to check RHEL5.32 UP/SMP, RHEL5.64
> > UP/SMP, RHEL4.32, RHEL4.64, RHEL6. Can do that in a week or so.
> 
> Its OK to remove LAPIC timer reinjection.
Applied. Thanks for checking!

--
			Gleb.

      reply	other threads:[~2013-05-14  9:10 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-28 11:27 [PATCH] KVM: x86: Remove support for reporting coalesced APIC IRQs Jan Kiszka
2013-04-28 11:43 ` Gleb Natapov
2013-04-28 12:00   ` [PATCH v2] " Jan Kiszka
2013-05-03  1:14     ` Marcelo Tosatti
2013-05-14  1:30       ` Marcelo Tosatti
2013-05-14  9:10         ` Gleb Natapov [this message]

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=20130514091017.GC20995@redhat.com \
    --to=gleb@redhat.com \
    --cc=jan.kiszka@web.de \
    --cc=kvm@vger.kernel.org \
    --cc=mtosatti@redhat.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 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.