qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Alexander Graf <agraf@suse.de>
To: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
Cc: amit.shah@redhat.com, qemu-devel@nongnu.org, quintela@redhat.com
Subject: Re: [Qemu-devel] [PATCH] Peek dont read for vmdescription
Date: Wed, 24 Jun 2015 00:01:36 +0200	[thread overview]
Message-ID: <5589D740.1010004@suse.de> (raw)
In-Reply-To: <20150623163706.GE2167@work-vm>



On 23.06.15 18:37, Dr. David Alan Gilbert wrote:
> * Alexander Graf (agraf@suse.de) wrote:
>>
>>
>> On 22.06.15 16:49, Dr. David Alan Gilbert (git) wrote:
>>> From: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
>>>
>>> The VMDescription section maybe after the EOF mark, the current code
>>> does a 'qemu_get_byte' and either gets the header byte identifying the
>>> description or an error (which it ignores).  Doing the 'get' upsets
>>> RDMA which hangs on old machine types without the VMDescription.
>>>
>>> Using 'qemu_peek_byte' avoids that.
>>>
>>> Signed-off-by: Dr. David Alan Gilbert <dgilbert@redhat.com>
>>
>> Fun. I did actually use peek at first and then figured it's the same as
>> read in the qemu file implementation. Have you figured out why exactly
>> peek does make a difference for the RDMA case?
> 
> Yeh, scrap this patch.
> 
> I've just posted 
> 
> 'Only try and read a VMDescription if it should be there'
> 
> as a replacement.
> Fundamentally, the trick of trying to send/read stuff after the EOF
> just isn't safe on all transports.  We've got to read stuff if it's
> expected and only if it's expected and obey the EOF marker.  If it
> wasn't for keeping compatibility I'd swing this section around so it
> went before the EOF, but we can't break compatibility with streams
> that already have it.

Meh, that's truly a shame. The post-things-after-EOF-hack sounded so
great...


Alex

      reply	other threads:[~2015-06-23 22:01 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-22 14:49 [Qemu-devel] [PATCH] Peek dont read for vmdescription Dr. David Alan Gilbert (git)
2015-06-22 22:18 ` Alexander Graf
2015-06-23  8:37   ` Dr. David Alan Gilbert
2015-06-23 16:37   ` Dr. David Alan Gilbert
2015-06-23 22:01     ` Alexander Graf [this message]

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=5589D740.1010004@suse.de \
    --to=agraf@suse.de \
    --cc=amit.shah@redhat.com \
    --cc=dgilbert@redhat.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 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).