From: Jan Kiszka <jan.kiszka@siemens.com>
To: Stefan Hajnoczi <stefanha@redhat.com>
Cc: Kevin Wolf <kwolf@redhat.com>,
Anthony Liguori <aliguori@us.ibm.com>,
Stefan Hajnoczi <stefanha@gmail.com>,
qemu-devel <qemu-devel@nongnu.org>,
liu ping fan <qemulist@gmail.com>, Alex Bligh <alex@alex.org.uk>,
Paolo Bonzini <pbonzini@redhat.com>,
MORITA Kazutaka <morita.kazutaka@lab.ntt.co.jp>,
Richard Henderson <rth@twiddle.net>
Subject: Re: [Qemu-devel] Using aio_poll for timer carrier threads
Date: Wed, 14 Aug 2013 11:05:29 +0200 [thread overview]
Message-ID: <520B4859.9050205@siemens.com> (raw)
In-Reply-To: <20130814085205.GB14914@stefanha-thinkpad.redhat.com>
On 2013-08-14 10:52, Stefan Hajnoczi wrote:
> On Tue, Aug 13, 2013 at 04:13:03PM +0200, Jan Kiszka wrote:
>> On 2013-08-13 15:45, Stefan Hajnoczi wrote:
>>> On Tue, Aug 13, 2013 at 09:56:17AM +0200, Jan Kiszka wrote:
>>> The details depend on your device, do you have a git repo I can look at
>>> to understand your device model?
>>
>> Pushed my hacks here:
>>
>> git://git.kiszka.org/qemu.git queues/rt.new3
>
> Excellent, thanks! Are you calling qemu_raise_irq() outside the global
> mutex and how is it protected?
By luck and via many exceptions, specifically by disabling of HPET
support (to avoid that it is involved in IRQ routing - or even used in
legacy mode) and by relying on the direct delivery to the kernel in KVM
mode. Yes, IRQ delivery is still a huge construction site for BQL-free
device models.
Jan
--
Siemens AG, Corporate Technology, CT RTC ITP SES-DE
Corporate Competence Center Embedded Linux
next prev parent reply other threads:[~2013-08-14 9:05 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-13 7:56 [Qemu-devel] Using aio_poll for timer carrier threads Jan Kiszka
2013-08-13 13:45 ` Stefan Hajnoczi
2013-08-13 14:13 ` Jan Kiszka
2013-08-14 0:48 ` liu ping fan
2013-08-14 8:52 ` Stefan Hajnoczi
2013-08-14 9:05 ` Jan Kiszka [this message]
2013-08-14 11:35 ` Stefan Hajnoczi
2013-08-14 12:32 ` Jan Kiszka
2013-08-19 12:00 ` Paolo Bonzini
2013-08-13 14:45 ` Paolo Bonzini
2013-08-13 14:54 ` Jan Kiszka
2013-08-19 13:21 ` Paolo Bonzini
2013-08-19 13:40 ` Jan Kiszka
2013-08-19 14:09 ` Paolo Bonzini
2013-08-19 13:58 ` Alex Bligh
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=520B4859.9050205@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=alex@alex.org.uk \
--cc=aliguori@us.ibm.com \
--cc=kwolf@redhat.com \
--cc=morita.kazutaka@lab.ntt.co.jp \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemulist@gmail.com \
--cc=rth@twiddle.net \
--cc=stefanha@gmail.com \
--cc=stefanha@redhat.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.