From: Jan Kiszka <jan.kiszka@web.de>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Avi Kivity <avi@redhat.com>,
linux-kernel <linux-kernel@vger.kernel.org>,
Marcelo Tosatti <mtosatti@redhat.com>,
KVM list <kvm@vger.kernel.org>
Subject: Re: [GIT PULL] KVM fixes for 3.5-rc6
Date: Sat, 14 Jul 2012 13:23:31 +0200 [thread overview]
Message-ID: <500156B3.6040205@web.de> (raw)
In-Reply-To: <alpine.LFD.2.02.1207141253490.32033@ionos>
[-- Attachment #1: Type: text/plain, Size: 731 bytes --]
On 2012-07-14 13:16, Thomas Gleixner wrote:
> On Sat, 14 Jul 2012, Jan Kiszka wrote:
>> On 2012-07-14 04:25, Thomas Gleixner wrote:
>> This patch here is a workaround to unbreak devices assignment in 3.5
>> after the IRQ layer changes without regressing noticeable /wrt overhead.
>
> Yeah, workaround and regression are the proper marketing buzzwords to
> excuse mindless hackery.
>
> It took me a minute to figure out that there is no reason at all to
> use a threaded interrupt handler for MSI and MSIX.
Thomas, we also explained to you in the cited thread that your simple
approach for this doesn't work as is. We will have a proper solution
soon, but it takes a bit more than a minute - at least us.
Jan
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 262 bytes --]
next prev parent reply other threads:[~2012-07-14 11:23 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-12 11:55 [GIT PULL] KVM fixes for 3.5-rc6 Avi Kivity
2012-07-13 15:45 ` Linus Torvalds
2012-07-13 15:58 ` Linus Torvalds
2012-07-13 18:28 ` Thomas Gleixner
2012-07-13 18:53 ` Linus Torvalds
2012-07-13 19:02 ` Thomas Gleixner
2012-07-25 10:53 ` [tip:irq/urgent] genirq: Allow irq chips to mark themself oneshot safe tip-bot for Thomas Gleixner
2012-07-14 2:25 ` [GIT PULL] KVM fixes for 3.5-rc6 Thomas Gleixner
2012-07-14 7:00 ` Jan Kiszka
2012-07-14 11:16 ` Thomas Gleixner
2012-07-14 11:23 ` Jan Kiszka [this message]
2012-07-14 12:33 ` Thomas Gleixner
2012-07-14 12:55 ` Jan Kiszka
2012-07-16 11:36 ` Avi Kivity
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=500156B3.6040205@web.de \
--to=jan.kiszka@web.de \
--cc=avi@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mtosatti@redhat.com \
--cc=tglx@linutronix.de \
--cc=torvalds@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