From: David Hildenbrand <david@redhat.com>
To: "Michal Prívozník" <mprivozn@redhat.com>, qemu-devel@nongnu.org
Cc: imammedo@redhat.com
Subject: Re: [PATCH] hostmem: Round up memory size for qemu_madvise() in host_memory_backend_memory_complete()
Date: Mon, 4 Dec 2023 19:38:59 +0100 [thread overview]
Message-ID: <9ef38722-0a49-4d4c-87da-56f6ea988050@redhat.com> (raw)
In-Reply-To: <7e70c5d4-8c18-4861-8aca-497ba940c839@redhat.com>
>>
>
> Fair enough. After all of this, I'm inclined to turn this into a proper
> error and deny not page aligned sizes. There's no real benefit in having
> them and furthermore, the original bug report is about cryptic error
> message.
>
I guess if we glue this to compat machines we should be definitely fine.
--
Cheers,
David / dhildenb
prev parent reply other threads:[~2023-12-04 18:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-27 12:32 [PATCH] hostmem: Round up memory size for qemu_madvise() in host_memory_backend_memory_complete() Michal Privoznik
2023-11-27 13:37 ` David Hildenbrand
2023-11-27 13:55 ` David Hildenbrand
2023-12-01 9:07 ` Michal Prívozník
2023-12-04 9:21 ` David Hildenbrand
2023-12-04 14:12 ` Michal Prívozník
2023-12-04 18:38 ` David Hildenbrand [this message]
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=9ef38722-0a49-4d4c-87da-56f6ea988050@redhat.com \
--to=david@redhat.com \
--cc=imammedo@redhat.com \
--cc=mprivozn@redhat.com \
--cc=qemu-devel@nongnu.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).