qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: "Marc Marí" <marc.mari.barcelo@gmail.com>,
	qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] QEMU and Real Time OS
Date: Fri, 30 Jan 2015 00:06:50 +0100	[thread overview]
Message-ID: <54CABD0A.1090207@redhat.com> (raw)
In-Reply-To: <20150129203728.6cb9271e@crunchbang>



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.

Paolo

  reply	other threads:[~2015-01-29 23:07 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 [this message]
2015-01-30  7:37   ` Jan Kiszka
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=54CABD0A.1090207@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=marc.mari.barcelo@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).