From: Andreas Mohr <andi@lisas.de>
To: Purcareata Bogdan <b43198@freescale.com>
Cc: benh@kernel.crashing.org, linuxppc-dev@lists.ozlabs.org,
linux-kernel@vger.kernel.org
Subject: Re: [RFC] PPC: MPIC: necessary readback after EOI?
Date: Mon, 5 Jan 2015 18:46:16 +0100 [thread overview]
Message-ID: <20150105174616.GA3159@rhlx01.hs-esslingen.de> (raw)
In-Reply-To: <54AA9C4D.3000001@freescale.com>
Hi,
> I was curious why the mpic_cpu_read(MPIC_INFO(CPU_WHOAMI)) was there in
> the first place and if it's still needed. If it's still required, I
> guess a better approach is to eliminate the call only if the kernel is
> running on the KVM guest side, where the MPIC is emulated and no longer
> requires a readback.
"Why not?"
A mechanism being "emulated"/"virtual" or not
may not necessarily be much of a distinction (if at all!).
The readback might be required
to properly fulfill all requirements
of a full state change protocol specification,
which might easily be the case for both RS(*) and virtual hardware.
And especially for virtual hardware
such a "readback" event
might be an extremely important "end of transaction" marker
which may often be needed for freeing of temporary resources etc.
I'm talking out of my *ss without any MPIC specifics here
(and especially not why the readback there actually is needed -
if that doesn't happen to be the case for PCI Posting reasons or some such),
but it's just intended as food for thought :)
*) Real Silicon (rather than RL - Real Life)
HTH,
Andreas Mohr
next prev parent reply other threads:[~2015-01-05 17:46 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-05 14:14 Purcareata Bogdan
2015-01-05 17:46 ` Andreas Mohr [this message]
2015-01-05 18:10 ` Scott Wood
2015-01-05 18:43 ` Andreas Mohr
2015-01-07 2:56 ` Scott Wood
2015-01-07 14:44 ` Benjamin Herrenschmidt
2015-01-07 17:04 ` Scott Wood
2015-01-08 19:17 ` Benjamin Herrenschmidt
2015-01-07 14:43 ` Benjamin Herrenschmidt
2015-01-07 14:40 ` Benjamin Herrenschmidt
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=20150105174616.GA3159@rhlx01.hs-esslingen.de \
--to=andi@lisas.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®