From: Sasha Levin <levinsasha928@gmail.com>
To: "Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>
Cc: penberg@kernel.org, kvm@vger.kernel.org
Subject: Re: [PATCH 1/5] tools/kvm/9p: Use the same #define as the kernel
Date: Sat, 18 Jun 2011 14:50:25 -0400 [thread overview]
Message-ID: <1308423025.3766.5.camel@lappy> (raw)
In-Reply-To: <1308419348-31934-1-git-send-email-aneesh.kumar@linux.vnet.ibm.com>
On Sat, 2011-06-18 at 23:19 +0530, Aneesh Kumar K.V wrote:
> Signed-off-by: Aneesh Kumar K.V <aneesh.kumar@linux.vnet.ibm.com>
> ---
> tools/kvm/virtio/9p.c | 8 ++++----
> 1 files changed, 4 insertions(+), 4 deletions(-)
>
> diff --git a/tools/kvm/virtio/9p.c b/tools/kvm/virtio/9p.c
> index 1545995..209760b 100644
> --- a/tools/kvm/virtio/9p.c
> +++ b/tools/kvm/virtio/9p.c
> @@ -20,7 +20,7 @@
> #include <net/9p/9p.h>
>
> #define NUM_VIRT_QUEUES 1
> -#define VIRTIO_P9_QUEUE_SIZE 128
> +#define VIRTQUEUE_NUM 128
The change is ok, but it should be vertically aligned with the rest of
the defines there.
> #define VIRTIO_P9_DEFAULT_TAG "kvm_9p"
> #define VIRTIO_P9_HDR_LEN (sizeof(u32)+sizeof(u8)+sizeof(u16))
> #define VIRTIO_P9_MAX_FID 128
> @@ -114,7 +114,7 @@ static bool virtio_p9_pci_io_in(struct ioport *ioport, struct kvm *kvm,
> ioport__write32(data, p9dev->vqs[p9dev->queue_selector].pfn);
> break;
> case VIRTIO_PCI_QUEUE_NUM:
> - ioport__write16(data, VIRTIO_P9_QUEUE_SIZE);
> + ioport__write16(data, VIRTQUEUE_NUM);
> break;
> case VIRTIO_PCI_STATUS:
> ioport__write8(data, p9dev->status);
> @@ -573,7 +573,7 @@ static bool virtio_p9_do_io_request(struct kvm *kvm, struct p9_dev_job *job)
> p9_handler *handler;
> struct virt_queue *vq;
> struct p9_dev *p9dev;
> - struct iovec iov[VIRTIO_P9_QUEUE_SIZE];
> + struct iovec iov[VIRTQUEUE_NUM];
>
> vq = job->vq;
> p9dev = job->p9dev;
> @@ -629,7 +629,7 @@ static bool virtio_p9_pci_io_out(struct ioport *ioport, struct kvm *kvm,
> queue->pfn = ioport__read32(data);
> p = guest_pfn_to_host(kvm, queue->pfn);
>
> - vring_init(&queue->vring, VIRTIO_P9_QUEUE_SIZE, p,
> + vring_init(&queue->vring, VIRTQUEUE_NUM, p,
> VIRTIO_PCI_VRING_ALIGN);
>
> *job = (struct p9_dev_job) {
--
Sasha.
next prev parent reply other threads:[~2011-06-18 18:50 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-18 17:49 [PATCH 1/5] tools/kvm/9p: Use the same #define as the kernel Aneesh Kumar K.V
2011-06-18 17:49 ` [PATCH 2/5] tools/kvm/virtio: Add new iov helper Aneesh Kumar K.V
2011-06-18 17:49 ` [PATCH 3/5] tools/kvm/9p: Don't follow symlink on server Aneesh Kumar K.V
2011-06-18 18:51 ` Sasha Levin
2011-06-19 5:17 ` Aneesh Kumar K.V
2011-06-19 6:41 ` Sasha Levin
2011-06-19 9:11 ` Aneesh Kumar K.V
2011-06-18 17:49 ` [PATCH 4/5] tools/kvm/9p: Fix the pdu len Aneesh Kumar K.V
2011-06-18 18:51 ` Sasha Levin
2011-06-19 5:11 ` Aneesh Kumar K.V
2011-06-19 6:41 ` Sasha Levin
2011-06-18 17:49 ` [PATCH 5/5] tools/kvm/9p: Simplify the handler Aneesh Kumar K.V
2011-06-18 18:51 ` Sasha Levin
2011-06-19 5:13 ` Aneesh Kumar K.V
2011-06-19 6:41 ` Sasha Levin
2011-06-18 18:50 ` Sasha Levin [this message]
2011-06-19 5:14 ` [PATCH 1/5] tools/kvm/9p: Use the same #define as the kernel Aneesh Kumar K.V
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=1308423025.3766.5.camel@lappy \
--to=levinsasha928@gmail.com \
--cc=aneesh.kumar@linux.vnet.ibm.com \
--cc=kvm@vger.kernel.org \
--cc=penberg@kernel.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