qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: Ladi Prosek <lprosek@redhat.com>, Amit Shah <amit.shah@redhat.com>
Cc: pagupta <pagupta@redhat.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] rng: switch request queue to QSIMPLEQ
Date: Fri, 4 Mar 2016 10:12:19 +0100	[thread overview]
Message-ID: <56D95173.9050108@redhat.com> (raw)
In-Reply-To: <CABdb737AUefTQLvMDGqpZnKqRw-vUPKx9GddG-LfZTMm0ck1Mg@mail.gmail.com>



On 04/03/2016 09:04, Ladi Prosek wrote:
>>> >> +    QSIMPLEQ_INIT(&s->requests);
>>> >>  }
>> >
>> > This init here isn't necessary, the accessors for the queue will take
>> > care of this.
> We are basically purging the queue here and we want to leave it in a
> consistent state. Without the QSIMPLEQ_INIT the queue head would
> become a pair of dangling pointers. Let me know if I misunderstood
> your comment.

It wouldn't, check out QSIMPLEQ_REMOVE_HEAD:

#define QSIMPLEQ_REMOVE_HEAD(head, field) do {
    if (((head)->sqh_first = (head)->sqh_first->field.sqe_next) == NULL)
        (head)->sqh_last = &(head)->sqh_first;
} while (/*CONSTCOND*/0)

The queue would become { NULL, &s->requests.sqh_first }.  So the
QSIMPLEQ_INIT is indeed redundant.

Paolo

  reply	other threads:[~2016-03-04  9:12 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-03 13:16 [Qemu-devel] [PATCH] rng: switch request queue to QSIMPLEQ Ladi Prosek
2016-03-03 13:34 ` Paolo Bonzini
2016-03-04  6:27 ` Amit Shah
2016-03-04  8:04   ` Ladi Prosek
2016-03-04  9:12     ` Paolo Bonzini [this message]
2016-03-04  9:19       ` Ladi Prosek
2016-03-04  9:27         ` Paolo Bonzini
2016-03-04  9:46           ` Amit Shah
2016-03-04  9:16     ` Amit Shah
2016-03-04  9:46 ` Amit Shah

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=56D95173.9050108@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=amit.shah@redhat.com \
    --cc=lprosek@redhat.com \
    --cc=pagupta@redhat.com \
    --cc=qemu-devel@nongnu.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).