From: "Michael S. Tsirkin" <mst@redhat.com>
To: linux-kernel@vger.kernel.org
Cc: Jason Wang <jasowang@redhat.com>,
virtualization@lists.linux-foundation.org
Subject: [PATCH v7 03/19] tools/virtio: define __KERNEL__
Date: Mon, 6 Apr 2020 21:07:32 -0400 [thread overview]
Message-ID: <20200407010700.446571-4-mst@redhat.com> (raw)
In-Reply-To: <20200407010700.446571-1-mst@redhat.com>
Even though we are building in userspace, we are emulating kernel bits.
Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
---
tools/virtio/Makefile | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/tools/virtio/Makefile b/tools/virtio/Makefile
index b587b9a7a124..ea6674307507 100644
--- a/tools/virtio/Makefile
+++ b/tools/virtio/Makefile
@@ -4,7 +4,7 @@ test: virtio_test vringh_test
virtio_test: virtio_ring.o virtio_test.o
vringh_test: vringh_test.o vringh.o virtio_ring.o
-CFLAGS += -g -O2 -Werror -Wall -I. -I../include/ -I ../../usr/include/ -Wno-pointer-sign -fno-strict-overflow -fno-strict-aliasing -fno-common -MMD -U_FORTIFY_SOURCE -include ../../include/linux/kconfig.h
+CFLAGS += -g -O2 -Werror -Wall -I. -I../include/ -I ../../usr/include/ -Wno-pointer-sign -fno-strict-overflow -fno-strict-aliasing -fno-common -MMD -U_FORTIFY_SOURCE -include ../../include/linux/kconfig.h -D__KERNEL__
vpath %.c ../../drivers/virtio ../../drivers/vhost
mod:
${MAKE} -C `pwd`/../.. M=`pwd`/vhost_test V=${V}
--
MST
next prev parent reply other threads:[~2020-04-07 1:07 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-07 1:07 [PATCH v7 00/19] virtio: alignment issues Michael S. Tsirkin
2020-04-07 1:07 ` [PATCH v7 01/19] tools/virtio: define aligned attribute Michael S. Tsirkin
2020-04-07 1:07 ` [PATCH v7 02/19] tools/virtio: make asm/barrier.h self contained Michael S. Tsirkin
2020-04-07 1:07 ` Michael S. Tsirkin [this message]
2020-04-07 1:07 ` [PATCH v7 04/19] virtio: add VIRTIO_RING_NO_LEGACY Michael S. Tsirkin
2020-04-07 1:07 ` [PATCH v7 05/19] virtgpu: pull in uaccess.h Michael S. Tsirkin
2020-04-07 1:07 ` [PATCH v7 06/19] virtio-rng: pull in slab.h Michael S. Tsirkin
2020-04-07 1:07 ` [PATCH v7 07/19] remoteproc: " Michael S. Tsirkin
2020-04-07 1:07 ` [PATCH v7 08/19] virtio_input: " Michael S. Tsirkin
2020-04-07 1:07 ` [PATCH v7 09/19] virtio: stop using legacy struct vring in kernel Michael S. Tsirkin
2020-04-07 1:07 ` [PATCH v7 10/19] vhost: force spec specified alignment on types Michael S. Tsirkin
2020-04-07 1:07 ` [PATCH v7 11/19] virtio: add legacy init/size APIs Michael S. Tsirkin
2020-04-07 1:07 ` [PATCH v7 12/19] virtio_ring: switch to virtio_legacy_init/size Michael S. Tsirkin
2020-04-07 1:07 ` [PATCH v7 13/19] tools/virtio: " Michael S. Tsirkin
2020-04-07 1:07 ` [PATCH v7 14/19] vop: " Michael S. Tsirkin
2020-04-07 1:08 ` [PATCH v7 15/19] remoteproc: " Michael S. Tsirkin
2020-04-07 1:08 ` [PATCH v7 16/19] mellanox: " Michael S. Tsirkin
2020-04-07 1:08 ` [PATCH v7 17/19] vhost: option to fetch descriptors through an independent struct Michael S. Tsirkin
2020-04-07 1:08 ` [PATCH v7 18/19] vhost: use batched version by default Michael S. Tsirkin
2020-04-07 1:08 ` [PATCH v7 19/19] vhost: batching fetches Michael S. Tsirkin
2020-04-07 3:41 ` [PATCH v7 00/19] virtio: alignment issues Jason Wang
2020-04-07 9:48 ` Michael S. Tsirkin
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=20200407010700.446571-4-mst@redhat.com \
--to=mst@redhat.com \
--cc=jasowang@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--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).