From: Jan Kiszka <jan.kiszka@siemens.com>
To: "Paolo Bonzini" <pbonzini@redhat.com>,
"Marc Marí" <marc.mari.barcelo@gmail.com>,
qemu-devel <qemu-devel@nongnu.org>
Cc: "KONRAD Frédéric" <fred.konrad@greensocs.com>,
"Marcelo Tosatti" <mtosatti@redhat.com>,
"Luiz Capitulino" <lcapitulino@redhat.com>
Subject: Re: [Qemu-devel] QEMU and Real Time OS
Date: Fri, 30 Jan 2015 08:37:47 +0100 [thread overview]
Message-ID: <54CB34CB.20805@siemens.com> (raw)
In-Reply-To: <54CABD0A.1090207@redhat.com>
On 2015-01-30 00:06, Paolo Bonzini wrote:
>
>
> On 29/01/2015 20:37, Marc Marí wrote:
>> Is this an expected behaviour? I can't see why.
>>
>> I'd like to know if there is a certain reason why it doesn't work. Or
>> if it should work and the problem is too much I/O overhead. Or any
>> other hint to understand it.
>
> It is due to latencies in the host. You need at least to use preempt-rt
> kernels in the host as well.
That alone won't help much. You also need to fine-tune the guest to
avoid running into QEMU locks that continuously synchronizes the guest
on things like VGA or disk I/O emulation.
When using KVM, thus being able to run VCPUs widely independent of each
other and the device models, you need to push cyclictest on an isolated
second virtual CPU of the guest. Luiz and Marcelo can probably confirm
this based on their ongoing experiments.
With TCG, we would first of all have to make it true SMP and independent
of the I/O device lock. That's what Frederic is working on [1].
Jan
[1] http://permalink.gmane.org/gmane.comp.emulators.qemu/314406
--
Siemens AG, Corporate Technology, CT RTC ITP SES-DE
Corporate Competence Center Embedded Linux
next prev parent reply other threads:[~2015-01-30 7:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-29 19:37 [Qemu-devel] QEMU and Real Time OS Marc Marí
2015-01-29 23:06 ` Paolo Bonzini
2015-01-30 7:37 ` Jan Kiszka [this message]
2015-01-30 10:26 ` Marc Marí
2015-01-30 10:36 ` Frederic Konrad
2015-01-30 10:40 ` Marc Marí
2015-01-30 10:47 ` Jan Kiszka
2015-02-02 20:08 ` Marcelo Tosatti
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=54CB34CB.20805@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=fred.konrad@greensocs.com \
--cc=lcapitulino@redhat.com \
--cc=marc.mari.barcelo@gmail.com \
--cc=mtosatti@redhat.com \
--cc=pbonzini@redhat.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).