[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <558A6E4E.90907@redhat.com>
Date: Wed, 24 Jun 2015 10:46:06 +0200
From: Paolo Bonzini <pbonzini@...hat.com>
To: "Wu, Feng" <feng.wu@...el.com>,
"kvm@...r.kernel.org" <kvm@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
CC: "mtosatti@...hat.com" <mtosatti@...hat.com>,
"alex.williamson@...hat.com" <alex.williamson@...hat.com>,
"eric.auger@...aro.org" <eric.auger@...aro.org>
Subject: Re: [v4 01/16] KVM: Extend struct pi_desc for VT-d Posted-Interrupts
On 24/06/2015 07:42, Wu, Feng wrote:
> Do you mean we don't use bitfields at all, or the following format is
> acceptable, in which, we use bitfileds as less as possible?
> union {
> struct
> {
> u16 on : 1, /* bit 256 - Outstanding Notification */
> sn : 1, /* bit 257 - Suppress Notification */
> rsvd_1 : 14; /* bit 271:258 - Reserved */
> u8 nv; /* bit 279:272 - Notification Vector */
> u8 rsvd_2; /* bit 287:280 - Reserved */
> u32 ndst; /* bit 319:288 - Notification Destination */
> };
> u64 control;
This is okay.
Paolo
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists