All of lore.kernel.org
 help / color / mirror / Atom feed
From: Volodymyr Babchuk <Volodymyr_Babchuk@epam.com>
To: "paul@xen.org" <paul@xen.org>
Cc: "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
	"David Woodhouse" <dwmw@amazon.co.uk>,
	"Stefano Stabellini" <sstabellini@kernel.org>,
	"Julien Grall" <julien@xen.org>,
	"Oleksandr Tyshchenko" <Oleksandr_Tyshchenko@epam.com>,
	"Anthony Perard" <anthony.perard@citrix.com>,
	"Kevin Wolf" <kwolf@redhat.com>,
	"Hanna Reitz" <hreitz@redhat.com>,
	"Marc-André Lureau" <marcandre.lureau@redhat.com>,
	"Paolo Bonzini" <pbonzini@redhat.com>,
	"Jason Wang" <jasowang@redhat.com>,
	"open list:X86 Xen CPUs" <xen-devel@lists.xenproject.org>,
	"open list:Block layer core" <qemu-block@nongnu.org>
Subject: Re: [PATCH v2 2/6] xen: backends: touch some XenStore nodes only if device...
Date: Wed, 22 Nov 2023 22:50:59 +0000	[thread overview]
Message-ID: <87fs0x1jxp.fsf@epam.com> (raw)
In-Reply-To: <02fcd3c2-afe2-43f4-8a15-7caa85a147f5@xen.org>


Hi Paul,

Paul Durrant <xadimgnik@gmail.com> writes:

> On 21/11/2023 22:10, Volodymyr Babchuk wrote:
>> was created by QEMU
>> Xen PV devices in QEMU can be created in two ways: either by QEMU
>> itself, if they were passed via command line, or by Xen toolstack. In
>> the latter case, QEMU scans XenStore entries and configures devices
>> accordingly.
>> In the second case we don't want QEMU to write/delete front-end
>> entries for two reasons: it might have no access to those entries if
>> it is running in un-privileged domain and it is just incorrect to
>> overwrite entries already provided by Xen toolstack, because toolstack
>> manages those nodes. For example, it might read backend- or frontend-
>> state to be sure that they are both disconnected and it is safe to
>> destroy a domain.
>> This patch checks presence of xendev->backend to check if Xen PV
>> device is acting as a backend (i.e. it was configured by Xen
>
> Technally *all* XenDevice objects are backends.
>

Yes, you are right of course. I'll rephrase this paragraph in the next
version.

-- 
WBR, Volodymyr

  parent reply	other threads:[~2023-11-22 22:51 UTC|newest]

Thread overview: 55+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-21 22:10 [PATCH v2 0/6] xen-arm: add support for virtio-pci Volodymyr Babchuk
2023-11-21 22:10 ` [PATCH v2 1/6] hw/xen: Set XenBackendInstance in the XenDevice before realizing it Volodymyr Babchuk
2023-11-22 15:54   ` Paul Durrant
2023-11-22 17:05   ` Paul Durrant
2023-11-22 22:44     ` Woodhouse, David
2023-11-22 22:44       ` Woodhouse, David via
2023-11-22 23:49       ` Volodymyr Babchuk
2023-11-22 23:55         ` Woodhouse, David
2023-11-22 23:55           ` Woodhouse, David via
2023-11-22 22:56     ` Volodymyr Babchuk
2023-11-22 23:04       ` David Woodhouse
2023-11-23  9:29         ` Paul Durrant
2023-11-21 22:10 ` [PATCH v2 2/6] xen: backends: touch some XenStore nodes only if device Volodymyr Babchuk
2023-11-22 11:07   ` Philippe Mathieu-Daudé
2023-11-22 22:49     ` Volodymyr Babchuk
2023-11-22 23:19       ` David Woodhouse
2023-11-22 17:03   ` Paul Durrant
2023-11-22 22:46     ` Woodhouse, David
2023-11-22 22:46       ` Woodhouse, David via
2023-11-22 22:50     ` Volodymyr Babchuk [this message]
2023-11-21 22:10 ` [PATCH v2 3/6] xen: xenstore: add possibility to preserve owner Volodymyr Babchuk
2023-11-22 17:07   ` Paul Durrant
2023-11-22 22:28     ` Stefano Stabellini
2023-11-22 23:01   ` David Woodhouse
2023-11-22 23:03     ` Volodymyr Babchuk
2023-11-23  1:19     ` Volodymyr Babchuk
2023-11-21 22:10 ` [PATCH v2 4/6] xen_pvdev: Do not assume Dom0 when creating a directory Volodymyr Babchuk
2023-11-22 17:11   ` Paul Durrant
2023-11-22 22:29     ` Stefano Stabellini
2023-11-22 23:03       ` David Woodhouse
2023-11-22 23:09         ` Stefano Stabellini
2023-11-22 23:11           ` David Woodhouse
2023-11-22 23:20             ` Stefano Stabellini
2023-11-22 23:46               ` Volodymyr Babchuk
2023-11-23  0:07                 ` Volodymyr Babchuk
2023-11-23  9:28                   ` Paul Durrant
2023-11-23 10:45                     ` David Woodhouse
2023-11-23 11:43                       ` Volodymyr Babchuk
2023-11-23 11:51                         ` David Woodhouse
2023-11-23 11:54                     ` Volodymyr Babchuk
2023-11-23 11:57                       ` David Woodhouse
2023-11-23 12:17                         ` Volodymyr Babchuk
2023-11-23 12:27                           ` David Woodhouse
2023-11-23 12:54                             ` Paul Durrant
2023-11-24  0:24                             ` Volodymyr Babchuk
2023-11-24 12:56                   ` Alex Bennée
2023-11-21 22:10 ` [PATCH v2 6/6] xen_arm: Add virtual PCIe host bridge support Volodymyr Babchuk
2023-11-22 22:39   ` Stefano Stabellini
2023-11-22 23:44     ` Vikram Garhwal
2023-11-23  0:11       ` Volodymyr Babchuk
2023-11-24 12:30   ` Igor Mammedov
2023-11-24 15:47     ` Volodymyr Babchuk
2023-11-21 22:10 ` [PATCH v2 5/6] xen_arm: Set mc->max_cpus to GUEST_MAX_VCPUS in xen_arm_init() Volodymyr Babchuk
2023-11-22 11:10   ` Philippe Mathieu-Daudé
2023-11-24 12:04   ` Igor Mammedov

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=87fs0x1jxp.fsf@epam.com \
    --to=volodymyr_babchuk@epam.com \
    --cc=Oleksandr_Tyshchenko@epam.com \
    --cc=anthony.perard@citrix.com \
    --cc=dwmw@amazon.co.uk \
    --cc=hreitz@redhat.com \
    --cc=jasowang@redhat.com \
    --cc=julien@xen.org \
    --cc=kwolf@redhat.com \
    --cc=marcandre.lureau@redhat.com \
    --cc=paul@xen.org \
    --cc=pbonzini@redhat.com \
    --cc=qemu-block@nongnu.org \
    --cc=qemu-devel@nongnu.org \
    --cc=sstabellini@kernel.org \
    --cc=xen-devel@lists.xenproject.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.