All of lore.kernel.org
 help / color / mirror / Atom feed
From: Samuel Thibault <samuel.thibault@ens-lyon.org>
To: "Marek Marczykowski-Górecki" <marmarek@invisiblethingslab.com>
Cc: HW42 <hw42@ipsumj.de>, xen-devel <xen-devel@lists.xen.org>
Subject: Re: PCI passthrough with stubdomain
Date: Fri, 23 Sep 2016 23:00:42 +0200	[thread overview]
Message-ID: <20160923210042.GA18469@var.home> (raw)
In-Reply-To: <20160923185643.GD31510@mail-itl>

Marek Marczykowski-Górecki, on Fri 23 Sep 2016 20:56:43 +0200, wrote:
> 1. How to do this? ;) I.e. what synchronization primitives are available
> in mini-os? Just pthread_mutex_lock/unlock?

pthread_mutex_lock are nops :o) because we don't have pthread_create.
But for mini-os itself there are synchronization primitives, yes:
there are also semaphores (./include/semaphore.h) and waitqueues
(include/wait.h).

> 2. Wouldn't the same problem be with other stubdomain implementations?
> Like Linux + qemu-xen or rumprun + qemu-xen? At least in Linux case
> pcifront driver will also needs some time for initialization...

Possibly, I don't know about them, they didn't exist at the time ;)

Samuel

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel

  reply	other threads:[~2016-09-23 21:00 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-23  8:48 PCI passthrough with stubdomain Marek Marczykowski-Górecki
2016-09-23  9:22 ` Jan Beulich
2016-09-23 13:27 ` Samuel Thibault
2016-09-23 14:25   ` Marek Marczykowski-Górecki
2016-09-23 14:51     ` Samuel Thibault
2016-09-23 18:56       ` Marek Marczykowski-Górecki
2016-09-23 21:00         ` Samuel Thibault [this message]
2016-09-23 21:04           ` Marek Marczykowski-Górecki
2016-09-23 15:35     ` Konrad Rzeszutek Wilk
2016-09-23 18:47       ` Marek Marczykowski-Górecki

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=20160923210042.GA18469@var.home \
    --to=samuel.thibault@ens-lyon.org \
    --cc=hw42@ipsumj.de \
    --cc=marmarek@invisiblethingslab.com \
    --cc=xen-devel@lists.xen.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 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.