From: Jianjun Duan <duanj@linux.vnet.ibm.com>
To: Paolo Bonzini <pbonzini@redhat.com>,
"Dr. David Alan Gilbert" <dgilbert@redhat.com>
Cc: qemu-devel@nongnu.org, qemu-ppc@nongnu.org, dmitry@daynix.com,
peter.maydell@linaro.org, kraxel@redhat.com, mst@redhat.com,
david@gibson.dropbear.id.au, veroniabahaa@gmail.com,
quintela@redhat.com, amit.shah@redhat.com, mreitz@redhat.com,
kwolf@redhat.com, rth@twiddle.net, aurelien@aurel32.net,
leon.alrae@imgtec.com, blauwirbel@gmail.com,
mark.cave-ayland@ilande.co.uk, mdroth@linux.vnet.ibm.com
Subject: Re: [Qemu-devel] [Qemu-ppc] [QEMU PATCH v6 2/2] migration: migrate QTAILQ
Date: Fri, 14 Oct 2016 09:43:19 -0700 [thread overview]
Message-ID: <d9f06534-e645-b993-93fe-1201d4884ca8@linux.vnet.ibm.com> (raw)
In-Reply-To: <897cd09c-dc83-202d-52af-8df381b967f2@redhat.com>
I need to double check my code. My build passed and migration test also
succeeded.
On 10/14/2016 04:07 AM, Paolo Bonzini wrote:
>
>
> On 14/10/2016 12:44, Dr. David Alan Gilbert wrote:
>>>> +#define QTAILQ_RAW_INSERT_TAIL(head, elm, entry) do { \
>>>> + *((void **) ((char *) (elm) + (entry) + QTAILQ_NEXT_OFFSET)) = NULL; \
>>>> + *((void **) ((char *) (elm) + (entry) + QTAILQ_PREV_OFFSET)) = \
>>>> + *((void **) ((char *) (head) + QTAILQ_LAST_OFFSET)); \
>>>> + **((void ***)((char *) (head) + QTAILQ_LAST_OFFSET)) = (elm); \
>>>> + *((void **) ((char *) (head) + QTAILQ_LAST_OFFSET)) = \
>>>> + (void *) ((char *) (elm) + (entry) + QTAILQ_NEXT_OFFSET); \
>>>> +} while (/*CONSTCOND*/0)
>> I wonder if there's a simpler way to do this; I'm not sure this works, but something like:
>>
>> struct QTAILQDummy {
>> char dummy;
>> };
>>
>> QTAILQ_HEAD(QTAILQRawHead, struct QTAILQDummy)
>> typedef QTAILQ_ENTRY(struct QTAILQDummy) QTAILQRawEntry;
>>
>> #define QTAILQ_RAW_FOREACH(elm, head, entry) \
>> for ((elm) = ((struct QTAILQRawHead *)head)->tqh_first) \
>> (elm); \
>> (elm) = \
>> (elm) = ((QTAILQRawEntry *)((char *) (elm) + (entry)))->tqh_next
>>
>> and then I think elm gets declared as a struct QTAILQDummy.
>> But it does avoid those FIRST_OFFSET/LAST_OFFSET/NEXT_OFFSET/PREV_OFFSET calculations.
>
> Another possibility is a macro like
>
> #define field_at_offset(base, offset, type) \
> ((type) (((char *) (base)) + (offset)))
>
> so that you can do
>
> *field_at_offset(void **, elm, (entry) + QTAILQ_NEXT_OFFSET) = NULL;
> *field_at_offset(void ***, elm, (entry) + QTAILQ_PREV_OFFSET) =
> *field_at_offset(void ***, head, QTAILQ_LAST_OFFSET);
> **field_at_offset(void ***, head, QTAILQ_LAST_OFFSET) = (elm);
> *field_at_offset(void ***, head, QTAILQ_LAST_OFFSET) =
> field_at_offset(void **, elm, (entry) + QTAILQ_NEXT_OFFSET);
The thing is that we don't know type at all. So only the offset values
is used. This is intended for QTAILQ of any type.
Thanks,
Jianjun
>
> or something like that (note that I've always used the same type for
> next and last, by the way).
>
> Paolo
>
next prev parent reply other threads:[~2016-10-14 16:43 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-13 21:30 [Qemu-devel] [QEMU PATCH v6 0/2] migration: migrate QTAILQ Jianjun Duan
2016-10-13 21:30 ` [Qemu-devel] [QEMU PATCH v6 1/2] migration: extend VMStateInfo Jianjun Duan
2016-10-14 9:23 ` Dr. David Alan Gilbert
2016-10-14 16:58 ` Jianjun Duan
2016-10-13 21:30 ` [Qemu-devel] [QEMU PATCH v6 2/2] migration: migrate QTAILQ Jianjun Duan
2016-10-14 10:44 ` Dr. David Alan Gilbert
2016-10-14 11:07 ` Paolo Bonzini
2016-10-14 16:43 ` Jianjun Duan [this message]
2016-10-14 18:39 ` [Qemu-devel] [Qemu-ppc] " Paolo Bonzini
2016-10-14 21:10 ` Jianjun Duan
2016-10-14 16:56 ` Jianjun Duan
2016-10-14 17:04 ` Dr. David Alan Gilbert
2016-10-14 17:18 ` Jianjun Duan
2016-10-15 12:48 ` Halil Pasic
2016-10-17 16:49 ` Jianjun Duan
2016-10-21 18:51 ` Dr. David Alan Gilbert
2016-10-21 19:16 ` Jianjun Duan
2016-10-14 2:01 ` [Qemu-devel] [QEMU PATCH v6 0/2] " no-reply
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=d9f06534-e645-b993-93fe-1201d4884ca8@linux.vnet.ibm.com \
--to=duanj@linux.vnet.ibm.com \
--cc=amit.shah@redhat.com \
--cc=aurelien@aurel32.net \
--cc=blauwirbel@gmail.com \
--cc=david@gibson.dropbear.id.au \
--cc=dgilbert@redhat.com \
--cc=dmitry@daynix.com \
--cc=kraxel@redhat.com \
--cc=kwolf@redhat.com \
--cc=leon.alrae@imgtec.com \
--cc=mark.cave-ayland@ilande.co.uk \
--cc=mdroth@linux.vnet.ibm.com \
--cc=mreitz@redhat.com \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@nongnu.org \
--cc=quintela@redhat.com \
--cc=rth@twiddle.net \
--cc=veroniabahaa@gmail.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).