From: Blue Swirl <blauwirbel@gmail.com>
To: Paul Brook <paul@codesourcery.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] Compile dma only once
Date: Sat, 29 May 2010 08:13:45 +0000 [thread overview]
Message-ID: <AANLkTiloZgAX-QpE908YAJ_orLL1n_W2WR-2TIdEAkTO@mail.gmail.com> (raw)
In-Reply-To: <201005282034.21254.paul@codesourcery.com>
[-- Attachment #1: Type: text/plain, Size: 1074 bytes --]
On Fri, May 28, 2010 at 7:34 PM, Paul Brook <paul@codesourcery.com> wrote:
>> Use a qemu_irq to request CPU exit.
>
> Needing to request a CPU exit at all is just wrong. See previous discussions
> about how any use of qemu_bh_schedule_idle is fundamentally broken.
I agree for the device case. Is the attached patch then OK?
But what about other uses (with the patch applied):
User emulator signal delivery:
/src/qemu/darwin-user/signal.c:216: cpu_exit(global_env);
/src/qemu/linux-user/signal.c:507: cpu_exit(thread_env);
qemu_notify_event():
/src/qemu/cpus.c:286: cpu_exit(env);
/src/qemu/cpus.c:289: cpu_exit(next_cpu);
Is that broken too and should be removed?
cpu_signal():
/src/qemu/cpus.c:531: cpu_exit(cpu_single_env);
vm_stop():
/src/qemu/cpus.c:733: cpu_exit(cpu_single_env);
KVM IO window exit:
/src/qemu/kvm-all.c:859: cpu_exit(env);
Some exclusive ARM operation:
/src/qemu/linux-user/main.c:152: cpu_exit(other);
ARM/m68k semihosting:
/src/qemu/gdbstub.c:2296: cpu_exit(s->c_cpu);
[-- Attachment #2: 0001-dma-remove-DMA_schedule-and-related-cpu_request_exi.patch --]
[-- Type: application/x-patch, Size: 8877 bytes --]
next prev parent reply other threads:[~2010-05-29 15:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-18 19:51 [Qemu-devel] [PATCH] Compile dma only once Blue Swirl
2010-05-28 19:34 ` Paul Brook
2010-05-29 8:13 ` Blue Swirl [this message]
2010-05-30 0:13 ` Paul Brook
-- strict thread matches above, loose matches on Subject: below --
2010-05-18 19:51 Blue Swirl
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=AANLkTiloZgAX-QpE908YAJ_orLL1n_W2WR-2TIdEAkTO@mail.gmail.com \
--to=blauwirbel@gmail.com \
--cc=paul@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).