From: "Blue Swirl" <blauwirbel@gmail.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Buggy wfi support for ARM user
Date: Sun, 8 Jun 2008 19:38:00 +0300 [thread overview]
Message-ID: <f43fc5580806080938y5490f0c9u300e44b12943ba9a@mail.gmail.com> (raw)
In-Reply-To: <761ea48b0806080907t311f83dbo7f181746920baecb@mail.gmail.com>
On 6/8/08, Laurent Desnogues <laurent.desnogues@gmail.com> wrote:
> >> I propose that for user mode this instruction be considered
> >> as a NOP. Any thoughts?
> >
> > Allowing usermode to issue WFI sounds like a bug.
>
> Here is a proposal that makes WFI no-ops for user mode emulation.
> Comments welcome, especially as I am not used to send patches :)
Generally, the config-host.mak part should be suppressed in patches.
I don't know about this WFI case or even much of ARM at all, but if
enabling WFI is controversial, maybe it could be implemented as a CPU
feature so that it is disabled by default.
next prev parent reply other threads:[~2008-06-08 16:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-08 12:54 [Qemu-devel] Buggy wfi support for ARM user Laurent Desnogues
2008-06-08 14:12 ` Paul Brook
2008-06-08 16:07 ` Laurent Desnogues
2008-06-08 16:38 ` Blue Swirl [this message]
2008-06-08 16:45 ` Laurent Desnogues
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=f43fc5580806080938y5490f0c9u300e44b12943ba9a@mail.gmail.com \
--to=blauwirbel@gmail.com \
--cc=qemu-devel@nongnu.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).