From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Geoff Levand <geoff@infradead.org>
Cc: linuxppc-dev <linuxppc-dev@lists.ozlabs.org>
Subject: Semantics of lv1_pause()
Date: Tue, 10 Jul 2012 13:20:02 +1000 [thread overview]
Message-ID: <1341890402.2561.2.camel@pasglop> (raw)
Hi Geoff !
Do you have access to any kind of documentation regarding the precise
semantics of lv1_pause() ?
I'm fixing various issues with our idle loops, among other things,
because we are soft-disabled when we hit ppc_md.powersave() but not
hard-disabled, there could be an interrupt marked as pending and not
taken yet.
Will that work properly ? I have this understanding that it might
not ... but heh.
Also if I call lv1_pause() with MSR_EE off, will it work ? Will it
return with MSR_EE on like H_CEDE does on pseries ?
Cheers,
Ben.
next reply other threads:[~2012-07-10 3:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-10 3:20 Benjamin Herrenschmidt [this message]
2012-07-10 19:36 ` Semantics of lv1_pause() Geoff Levand
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=1341890402.2561.2.camel@pasglop \
--to=benh@kernel.crashing.org \
--cc=geoff@infradead.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;
as well as URLs for NNTP newsgroup(s).