All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dong Liu <dliu.cn@gmail.com>
To: Sven-Thorsten Dietrich <sven@thebigcorporation.com>
Cc: linux-rt-users@vger.kernel.org
Subject: Re: RT patch and XEN
Date: Wed, 27 Jun 2012 23:16:42 -0400	[thread overview]
Message-ID: <4FEBCC9A.8070505@gmail.com> (raw)
In-Reply-To: <A4673A1C-DBAE-4FF1-B9DF-428C47A37D0C@thebigcorporation.com>

On 6/27/12 7:04 PM, Sven-Thorsten Dietrich wrote:
>
> On Jun 27, 2012, at 1:52 PM, Dong Liu wrote:
>
>> Hi,
>>
>> I tried to run PREEMPT_RT patch under XEN, but running into some problem.
>>
>> My kernel is 3.4.3 with -r11 patch. XEN is 4.1.2. The kernel is running file as dom0. But as a Paravirtual (PV) domU, the system crashes normal when there is network traffic. kernel message indicates is kernel/rtmutex_common.h:75, which is,
>>
>>        BUG_ON(w->lock != lock);
>>
>> Is this a known problem?
>
> I would consider this hopeless.
>
> Xen will not get you RT performance nor full preemption, so there is no point in running RT on Xen.
>
> Use KVM
>
> Sven
>

I also thought of that, because the RT performance or full preemption 
also depends on Xen's code, scheduler and spin lock etc. But I just want 
to have a system for benchmark comparison.

Running the RT kernel as HVM guest is fine.

Thanks!

Dong

  reply	other threads:[~2012-06-28  3:16 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-27 20:52 RT patch and XEN Dong Liu
2012-06-27 23:04 ` Sven-Thorsten Dietrich
2012-06-28  3:16   ` Dong Liu [this message]
  -- strict thread matches above, loose matches on Subject: below --
2018-04-30 11:05 RT Patch and Xen Iain Hunter
2018-05-07 13:15 ` Sebastian Andrzej Siewior
2018-05-08 15:55   ` Iain Hunter
2018-05-15 14:03     ` Sebastian Andrzej Siewior
2018-06-19 16:19       ` Iain Hunter
2018-06-19 16:26         ` Sebastian Andrzej Siewior

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=4FEBCC9A.8070505@gmail.com \
    --to=dliu.cn@gmail.com \
    --cc=linux-rt-users@vger.kernel.org \
    --cc=sven@thebigcorporation.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.