From: Filip Navara <filip.navara@gmail.com>
To: Nathan Froyd <froydnj@codesourcery.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] [RFC] cleanup cpu-exec.c: consolidate handle_cpu_signal
Date: Sat, 1 Aug 2009 22:42:09 +0200 [thread overview]
Message-ID: <5b31733c0908011342q12cd08acwe0fe966a935dfc63@mail.gmail.com> (raw)
In-Reply-To: <1240364008-7065-1-git-send-email-froydnj@codesourcery.com>
On Wed, Apr 22, 2009 at 3:33 AM, Nathan Froyd<froydnj@codesourcery.com> wrote:
> handle_cpu_signal is very nearly copy-paste code for each target, with a
> few minor variations. This patch sets up appropriate defaults for a
> generic handle_cpu_signal and provides overrides for particular targets
> that did things differently. Fixing things like the persistent (XXX:
> use sigsetjmp) should now become somewhat easier.
>
> I don't understand what the "activate soft MMU for this block" is trying
> to do. (Especially since handle_cpu_signal and company are under
> !defined(CONFIG_SOFTMMU)...) Even though it appears that if
> cpu_*_handle_mmu_fault ever returns a value > 0, that value is always
> one and therefore that block is superfluous, I've left that cleanup for
> a later time. Likewise for why x86 has a different EXCEPTION_ACTION
> than everyone else.
>
> Signed-off-by: Nathan Froyd <froydnj@codesourcery.com>
Any plans on reviving this patch? It's definitely a cleanup I am interested in.
Best regards,
Filip Navara
next prev parent reply other threads:[~2009-08-01 20:42 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-22 1:33 [Qemu-devel] [PATCH] [RFC] cleanup cpu-exec.c: consolidate handle_cpu_signal Nathan Froyd
2009-04-30 16:10 ` Paul Brook
2009-04-30 16:34 ` Avi Kivity
2009-04-30 17:07 ` Paul Brook
2009-04-30 17:56 ` Avi Kivity
2009-04-30 18:52 ` Blue Swirl
2009-04-30 18:57 ` Avi Kivity
2009-04-30 19:05 ` Blue Swirl
2009-04-30 20:52 ` Laurent Desnogues
2009-08-01 20:42 ` Filip Navara [this message]
2009-08-03 15:59 ` Nathan Froyd
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=5b31733c0908011342q12cd08acwe0fe966a935dfc63@mail.gmail.com \
--to=filip.navara@gmail.com \
--cc=froydnj@codesourcery.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).