From: Alexander Atanasov <alexander.atanasov@virtuozzo.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: David Hildenbrand <david@redhat.com>,
Jason Wang <jasowang@redhat.com>,
kernel@openvz.org, virtualization@lists.linux-foundation.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/1] Create debugfs file with virtio balloon usage information
Date: Tue, 28 Jun 2022 12:07:05 +0300 [thread overview]
Message-ID: <00e716d9-3ef8-a3b2-e1a9-26ddaadf3ea3@virtuozzo.com> (raw)
In-Reply-To: <20220627163714-mutt-send-email-mst@kernel.org>
Hello,
On 27/06/2022 23:42, Michael S. Tsirkin wrote:
> On Mon, Jun 27, 2022 at 07:19:09PM +0000, Alexander Atanasov wrote:
>> Allow the guest to know how much it is ballooned by the host.
>> It is useful when debugging out of memory conditions.
>>
>> When host gets back memory from the guest it is accounted
>> as used memory in the guest but the guest have no way to know
>> how much it is actually ballooned.
>>
>> No pretty printing and fixed as per coding style.
>> ....
>> +static int virtio_balloon_debug_show(struct seq_file *f, void *offset)
>> +{
>> + struct virtio_balloon *b = f->private;
>> + u32 num_pages;
>> + struct sysinfo i;
>> +
>> + si_meminfo(&i);
>> +
>> + seq_printf(f, "%-22s: %llx\n", "capabilities", b->vdev->features);
> why do we need this in debugfs? Isn't this available in sysfs already?
Yes, it doesn't make sense to have it without pretty printing. I will
remove it.
>> + seq_printf(f, "%-22s: %d\n", "page_size", 4096);
> I suspect this function doesn't work properly when page size is not 4K.
It is the page size used by the balloon and it is always 4K and not the
page size used by the guest which can be different.
/*
* Balloon device works in 4K page units. So each page is pointed to by
* multiple balloon pages. All memory counters in this driver are in
balloon
* page units.
*/
And the code agrees with the comment. To be consistent the file must use
the same units.
>> +
>> + virtio_cread_le(b->vdev, struct virtio_balloon_config, actual,
>> + &num_pages);
>> + /* Memory returned to host or amount we can inflate if possible */
>> + seq_printf(f, "%-22s: %u\n", "ballooned_pages", num_pages);
> I don't really get the comment here.
I will try to reword it to be more clear .
/*
* Pages allocated by host from the guest memory.
* Host inflates the balloon to get more memory.
* Guest needs to deflate the balloon to get more memory.
*/
>> + /* Total Memory for the guest from host */
>> + seq_printf(f, "%-22s: %lu\n", "total_pages", i.totalram);
>> +
>> + /* Current memory for the guest */
>> + seq_printf(f, "%-22s: %lu\n", "current_pages", i.totalram - num_pages);
> Are you sure these are in units of 4Kbyte pages?
The guest can have a different page size, so a conversion to balloon
page size is required - fix in the following patch .
--
Regards,
Alexander Atanasov
next prev parent reply other threads:[~2022-06-28 9:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-27 12:20 alexander.atanasov
2022-06-27 12:59 ` Michael S. Tsirkin
2022-06-27 19:19 ` Alexander Atanasov
2022-06-27 20:42 ` Michael S. Tsirkin
2022-06-28 9:07 ` Alexander Atanasov [this message]
2022-06-28 9:23 ` [PATCH v3 " Alexander Atanasov
2022-06-28 12:55 ` Vasily Averin
2022-06-28 13:03 ` Alexander Atanasov
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=00e716d9-3ef8-a3b2-e1a9-26ddaadf3ea3@virtuozzo.com \
--to=alexander.atanasov@virtuozzo.com \
--cc=david@redhat.com \
--cc=jasowang@redhat.com \
--cc=kernel@openvz.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mst@redhat.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
all inboxes | Powered by JetHome®