All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Xu <peterx@redhat.com>
To: "manish.mishra" <manish.mishra@nutanix.com>
Cc: qemu-devel@nongnu.org, berrange@redhat.com,
	prerna.saxena@nutanix.com, quintela@redhat.com
Subject: Re: [PATCH v2] migration: check magic value for deciding the mapping of channels
Date: Tue, 15 Nov 2022 15:06:38 -0500	[thread overview]
Message-ID: <Y3PxTgrkU96ir000@x1n> (raw)
In-Reply-To: <a027006d-48f7-4d8d-465a-a726bbdc6fbf@nutanix.com>

On Tue, Nov 15, 2022 at 11:29:13PM +0530, manish.mishra wrote:
> > > +   while (bytes < nbytes) {
> > > +       bytes = klass->io_read_peek(ioc,
> > > +                                   buf,
> > > +                                   nbytes,
> > > +                                   errp);
> > IIUC here you need to accumulate bytes rather than directly reusing it, so
> > e.g. two reads on 2 bytes each will satisfy a 4 bytes read.
> 
> Actually peek always reads from top so even if there are multile reads it
> does not accumulate.

Fair enough.

[...]

> Thank you Peter for review. I see this patch is included by Juan too in
> some other patch series of 30 patches, so how it will work. Do i need to
> send a independent V3 for this? Or it should be reviewed in that series.

From what I see right now, feel free to rework on new versions.  Please
also consider copying Dave (dgilbert@redhat.com) and Leonardo
(lsoaresp@redhat.com) on future posts.

Thanks,

-- 
Peter Xu



  reply	other threads:[~2022-11-15 20:07 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-07 16:51 [PATCH v2] migration: check magic value for deciding the mapping of channels manish.mishra
2022-11-08 11:15 ` manish.mishra
2022-11-10 12:29 ` manish.mishra
2022-11-10 22:47   ` Peter Xu
2022-11-11  7:31     ` manish.mishra
2022-11-15 17:36 ` Peter Xu
2022-11-15 17:59   ` manish.mishra
2022-11-15 20:06     ` Peter Xu [this message]
2022-11-15 18:11 ` Daniel P. Berrangé
2022-11-15 18:50   ` Daniel P. Berrangé
2022-11-16 11:19     ` manish.mishra
2022-11-16 11:27       ` Daniel P. Berrangé
2022-11-16 11:40         ` manish.mishra

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=Y3PxTgrkU96ir000@x1n \
    --to=peterx@redhat.com \
    --cc=berrange@redhat.com \
    --cc=manish.mishra@nutanix.com \
    --cc=prerna.saxena@nutanix.com \
    --cc=qemu-devel@nongnu.org \
    --cc=quintela@redhat.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.