qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: David Woodhouse <dwmw2@infradead.org>
To: Volodymyr Babchuk <Volodymyr_Babchuk@epam.com>,
	"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Cc: "Stefano Stabellini" <sstabellini@kernel.org>,
	"Julien Grall" <julien@xen.org>, "Paul Durrant" <paul@xen.org>,
	"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 v4 1/6] hw/xen: Set XenBackendInstance in the XenDevice before realizing it
Date: Fri, 26 Jan 2024 12:09:20 +0000	[thread overview]
Message-ID: <f61da5b48fecf07e67a4e64419af6e14f05d7cdf.camel@infradead.org> (raw)
In-Reply-To: <20231202014108.2017803-2-volodymyr_babchuk@epam.com>

[-- Attachment #1: Type: text/plain, Size: 1063 bytes --]

On Sat, 2023-12-02 at 01:41 +0000, Volodymyr Babchuk wrote:
> From: David Woodhouse <dwmw@amazon.co.uk>
> 
> This allows a XenDevice implementation to know whether it was created
> by QEMU, or merely discovered in XenStore after the toolstack created
> it. This will allow us to create frontend/backend nodes only when we
> should, rather than unconditionally attempting to overwrite them from
> a driver domain which doesn't have privileges to do so.
> 
> As an added benefit, it also means we no longer have to call the
> xen_backend_set_device() function from the device models immediately
> after calling qdev_realize_and_unref(). Even though we could make
> the argument that it's safe to do so, and the pointer to the unreffed
> device *will* actually still be valid, it still made my skin itch to
> look at it.
> 
> Signed-off-by: David Woodhouse <dwmw@amazon.co.uk>
> Reviewed-by: Paul Durrant <paul@xen.org>

I still have this lying around in my working tree. Shall I forget all
about it and let you take it with this patch series? 

[-- Attachment #2: smime.p7s --]
[-- Type: application/pkcs7-signature, Size: 5965 bytes --]

  reply	other threads:[~2024-01-26 12:09 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-02  1:41 [PATCH v4 0/6] xen-arm: add support for virtio-pci Volodymyr Babchuk
2023-12-02  1:41 ` [PATCH v4 2/6] xen: backends: don't overwrite XenStore nodes created by toolstack Volodymyr Babchuk
2023-12-06 17:10   ` Anthony PERARD
2023-12-02  1:41 ` [PATCH v4 1/6] hw/xen: Set XenBackendInstance in the XenDevice before realizing it Volodymyr Babchuk
2024-01-26 12:09   ` David Woodhouse [this message]
2023-12-02  1:41 ` [PATCH v4 3/6] xen: decouple generic xen code from legacy backends codebase Volodymyr Babchuk
2023-12-04 14:50   ` Paul Durrant
2023-12-02  1:41 ` [RFC PATCH v4 4/6] xen: add option to disable legacy backends Volodymyr Babchuk
2023-12-12 15:46   ` Anthony PERARD
2023-12-02  1:41 ` [PATCH v4 6/6] xen_arm: Add virtual PCIe host bridge support Volodymyr Babchuk
2023-12-02  1:41 ` [PATCH v4 5/6] xen_arm: set mc->max_cpus to GUEST_MAX_VCPUS Volodymyr Babchuk

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=f61da5b48fecf07e67a4e64419af6e14f05d7cdf.camel@infradead.org \
    --to=dwmw2@infradead.org \
    --cc=Volodymyr_Babchuk@epam.com \
    --cc=anthony.perard@citrix.com \
    --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 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).