From: Richard Henderson <rth@twiddle.net>
To: Chris Metcalf <cmetcalf@ezchip.com>,
gang.chen.5i5j@gmail.com, peter.maydell@linaro.org
Cc: qemu-devel@nongnu.org, xili_gchen_5257@hotmail.com
Subject: Re: [Qemu-devel] [PATCH v3] target-tilegx: Support iret instruction and related special registers
Date: Fri, 2 Oct 2015 12:26:59 +1000 [thread overview]
Message-ID: <560DEB73.6020609@twiddle.net> (raw)
In-Reply-To: <560DDE8D.8040202@ezchip.com>
On 10/02/2015 11:31 AM, Chris Metcalf wrote:
>
> It disables interrupts from being delivered. This means asynchronous
> interrupts get deferred until ICS is set back to zero, and synchronous
> interrupts (page fault, etc) cause a double-fault instead. ICS is automatically
> set on entry to interrupt handlers, so the handler has time to acquire any
> information about the interrupt from SPRs, and it is expected that ICS is
> cleared as soon as possible. ICS can also be used before returning from
> interrupts if you need to do something like adjust the interrupt mask prior to
> returning.
Which is all very well and good for supervisor mode... but what's it good for
in user mode?
I was about to quote you from 2012 (https://lkml.org/lkml/2012/3/30/994):
> In general we want to avoid ever touching memory while within an
> interrupt critical section, since the page fault path goes through
> a different path from the hypervisor when in an interrupt critical
> section, and we carefully decided with tilegx that we didn't need
> to support this path in the kernel.
Which implies that tilegx userland does nothing at all with ICS, and is in fact
unsupported?
r~
next prev parent reply other threads:[~2015-10-02 2:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-01 12:37 [Qemu-devel] [PATCH v3] target-tilegx: Support iret instruction and related special registers gang.chen.5i5j
2015-10-02 0:36 ` Richard Henderson
[not found] ` <560DDC06.9060002@hotmail.com>
2015-10-02 1:19 ` Chen Gang
2015-10-02 1:31 ` Chris Metcalf
2015-10-02 2:02 ` Chen Gang
2015-10-02 2:26 ` Richard Henderson [this message]
2015-10-02 14:37 ` Chris Metcalf
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=560DEB73.6020609@twiddle.net \
--to=rth@twiddle.net \
--cc=cmetcalf@ezchip.com \
--cc=gang.chen.5i5j@gmail.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=xili_gchen_5257@hotmail.com \
/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.