From: Segher Boessenkool <segher@kernel.crashing.org>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: linuxppc-dev@lists.ozlabs.org,
Purcareata Bogdan <b43198@freescale.com>,
linux-kernel@vger.kernel.org
Subject: Re: [RFC] PPC: MPIC: necessary readback after EOI?
Date: Wed, 7 Jan 2015 18:49:08 -0600 [thread overview]
Message-ID: <20150108004908.GA11770@gate.crashing.org> (raw)
In-Reply-To: <1420641610.5830.29.camel@kernel.crashing.org>
On Wed, Jan 07, 2015 at 03:40:10PM +0100, Benjamin Herrenschmidt wrote:
> One way to work around the performance loss for you would be to add some
> DT property to indicate to the guest that the read isn't necessary.
Or KVM could use a virtual interrupt controller better suited to its
needs.
Segher
WARNING: multiple messages have this Message-ID (diff)
From: Segher Boessenkool <segher@kernel.crashing.org>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: Purcareata Bogdan <b43198@freescale.com>,
linuxppc-dev@lists.ozlabs.org, linux-kernel@vger.kernel.org
Subject: Re: [RFC] PPC: MPIC: necessary readback after EOI?
Date: Wed, 7 Jan 2015 18:49:08 -0600 [thread overview]
Message-ID: <20150108004908.GA11770@gate.crashing.org> (raw)
In-Reply-To: <1420641610.5830.29.camel@kernel.crashing.org>
On Wed, Jan 07, 2015 at 03:40:10PM +0100, Benjamin Herrenschmidt wrote:
> One way to work around the performance loss for you would be to add some
> DT property to indicate to the guest that the read isn't necessary.
Or KVM could use a virtual interrupt controller better suited to its
needs.
Segher
next prev parent reply other threads:[~2015-01-08 0:49 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-05 14:14 [RFC] PPC: MPIC: necessary readback after EOI? Purcareata Bogdan
2015-01-05 14:14 ` Purcareata Bogdan
2015-01-05 17:46 ` Andreas Mohr
2015-01-05 17:46 ` Andreas Mohr
2015-01-05 18:10 ` Scott Wood
2015-01-05 18:10 ` Scott Wood
2015-01-05 18:43 ` Andreas Mohr
2015-01-05 18:43 ` Andreas Mohr
2015-01-07 2:56 ` Scott Wood
2015-01-07 2:56 ` Scott Wood
2015-01-07 14:44 ` Benjamin Herrenschmidt
2015-01-07 14:44 ` Benjamin Herrenschmidt
2015-01-07 17:04 ` Scott Wood
2015-01-07 17:04 ` Scott Wood
2015-01-08 19:17 ` Benjamin Herrenschmidt
2015-01-08 19:17 ` Benjamin Herrenschmidt
2015-01-07 14:43 ` Benjamin Herrenschmidt
2015-01-07 14:43 ` Benjamin Herrenschmidt
2015-01-07 14:40 ` Benjamin Herrenschmidt
2015-01-08 0:49 ` Segher Boessenkool [this message]
2015-01-08 0:49 ` Segher Boessenkool
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=20150108004908.GA11770@gate.crashing.org \
--to=segher@kernel.crashing.org \
--cc=b43198@freescale.com \
--cc=benh@kernel.crashing.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.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 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.