From: "Michael S. Tsirkin" <mst@redhat.com>
To: Sudip Mukherjee <sudipm.mukherjee@gmail.com>
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
kvm@vger.kernel.org, virtualization@lists.linux-foundation.org
Subject: Re: vhost: build failure
Date: Wed, 16 Sep 2015 11:36:45 +0300 [thread overview]
Message-ID: <20150916112119-mutt-send-email-mst@redhat.com> (raw)
In-Reply-To: <20150916082008.GA28512@sudip-pc>
On Wed, Sep 16, 2015 at 01:50:08PM +0530, Sudip Mukherjee wrote:
> Hi,
> While crosscompiling the kernel for openrisc with allmodconfig the build
> failed with the error:
> drivers/vhost/vhost.c: In function 'vhost_vring_ioctl':
> drivers/vhost/vhost.c:818:3: error: call to '__compiletime_assert_818' declared with attribute error: BUILD_BUG_ON failed: __alignof__
> *vq->avail > VRING_AVAIL_ALIGN_SIZE
>
> Can you please give me any idea about what the problem might be and how
> it can be solved.
>
> You can see the build log at:
> https://travis-ci.org/sudipm-mukherjee/parport/jobs/80365425
>
> regards
> sudip
Yes - I think I saw this already.
I think the openrisc cross-compiler is broken.
VRING_AVAIL_ALIGN_SIZE is 2
*vq->avail is:
struct vring_avail {
__virtio16 flags;
__virtio16 idx;
__virtio16 ring[];
};
And __virtio16 is just a u16 with some sparse annotations.
Looking at openrisc architecture document:
Operand: Length addr[3:0] if aligned
Halfword (or half) 2 bytes Xxx0
Type C-TYPE Sizeof Alignment Openrisc Equivalent
Short Signed short 2 2 Signed halfword
and
16.1.2
Aggregates and Unions
Aggregates (structures and arrays) and unions assume the alignment of their most
strictly aligned element.
So to me, it looks like your gcc violates the ABI
by adding alignment requirements > 2.
--
MST
next prev parent reply other threads:[~2015-09-16 8:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-16 8:20 vhost: build failure Sudip Mukherjee
2015-09-16 8:36 ` Michael S. Tsirkin [this message]
2015-09-16 9:50 ` Sudip Mukherjee
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=20150916112119-mutt-send-email-mst@redhat.com \
--to=mst@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=sudipm.mukherjee@gmail.com \
--cc=virtualization@lists.linux-foundation.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).