[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Qemu-devel] Re: virtio: Add memory statistics reporting to the ball

From: Anthony Liguori
Subject: Re: [Qemu-devel] Re: virtio: Add memory statistics reporting to the balloon driver (V2)
Date: Wed, 18 Nov 2009 09:02:26 -0600
User-agent: Thunderbird (X11/20090825)

Rusty Russell wrote:
On Wed, 18 Nov 2009 07:06:29 am Adam Litke wrote:
virtio: Add memory statistics reporting to the balloon driver (V2)

Changes since V1:
 - Use a virtqueue instead of the device config space

Hi Adam,

    If Anthony's happy, I'm happy with this approach.

Couple of minor points:

+static inline void update_stat(struct virtio_balloon *vb, int idx,
+                               unsigned int tag, unsigned long val)
+       BUG_ON(idx >= VIRTIO_BALLOON_S_NR);
+       vb->stats[idx].tag = tag;
+       vb->stats[idx].val = cpu_to_le32(val);

The little-endian conversion of the balloon driver is a historical mistake
(no other driver does this).  Let's not extend it to the stats.

I think the mistake is that the other drivers don't do that.

We cheat in qemu and assume that the guest is always in a fixed endianness but this is not always the case for all architectures.

That said, since we make this mistake everywhere, I guess I understand the argument to have consistency and to just admit that we're broken here. But this is where the endianness bits come from.

Here you've done one and not the other, which is even worse.  (Sparse would
have found this, I assume).

Yup, that's definitely wrong.

+struct virtio_balloon_stat
+       __le16 tag;
+       __le32 val;

Is 32 bits sufficient?  A big machine might get over 4bn faults, and certainly
4 TB of memory isn't that far away.

I think making the interface u64 and byte based would be the best solution. Making assumptions about page size across guest and host is another thing we should try to avoid.


Anthony Liguori

reply via email to

[Prev in Thread] Current Thread [Next in Thread]