From: Thomas Gleixner <tglx@linutronix.de>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: 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 04:25:49 +0200 (CEST) [thread overview]
Message-ID: <alpine.LFD.2.02.1207140208270.32033@ionos> (raw)
In-Reply-To: <alpine.LFD.2.02.1207131928000.32033@ionos>
On Fri, 13 Jul 2012, Thomas Gleixner wrote:
> On Fri, 13 Jul 2012, Linus Torvalds wrote:
> > On Fri, Jul 13, 2012 at 8:45 AM, Linus Torvalds
> > <torvalds@linux-foundation.org> wrote:
> > At the same time, I do wonder if maybe MSI + IRQF_ONESHOT couldn't be
> > improved. The fact that the KVM people think that the extra overhead
> > of IRQF_ONESHOT is a bad thing for MSI interrupts makes me wonder if
> > maybe this wouldn't be an area the irq layer couldn't be improved on.
> > Maybe the MSI+IRQF_ONESHOT case could be improved. Because MSI is kind
> > of fundamentally one-shot, since it's a message-based irq scheme. So
> > maybe the extra overhead is unnecessary in general, not just in this
> > particular KVM case. Hmm?
> >
> > Thomas, see the commentary of a76beb14123a ("KVM: Fix device
> > assignment threaded irq handler").
>
> Groan.
>
> We already discussed to let the irq chip (in this case MSI) tell the
> core that it does not need the extra oneshot handling. That way the
> code which requests an threaded irq with the NULL primary handler
> works on both MSI and normal interrupts.
That's the kind of stuff which makes me go berserk, and just for the
record: the most complaints I get for going berserk are coming from
the virt folks.
I really can't understand why the virt folks think they are
special and do not have to talk to core maintainers.
Back then when I was doing the big irq cleanup, virt crap stood out by
far with the most idiotic^Wcreative "workarounds". Of course nobody
complained about me being moronic enough to come up with generic
solutions for their problems.
Though especially that commit including its changelog proves once
again the ignorance and desinterest of the virt crowd in solving
problems which are not only relevant to themself.
I whish you'd just refused to pull that nonsense and instead made them
talk to those folks who had a proper solution in mind already.
In fact we could have solved that proper weeks ago, if only people
would have raised the issue.
I'm tired of that kind of crap, really.
Thomas
next prev parent reply other threads:[~2012-07-14 2:25 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-12 11:55 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 ` Thomas Gleixner [this message]
2012-07-14 7:00 ` [GIT PULL] KVM fixes for 3.5-rc6 Jan Kiszka
2012-07-14 11:16 ` Thomas Gleixner
2012-07-14 11:23 ` Jan Kiszka
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=alpine.LFD.2.02.1207140208270.32033@ionos \
--to=tglx@linutronix.de \
--cc=avi@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mtosatti@redhat.com \
--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
Powered by JetHome