From: David Hildenbrand <david@redhat.com>
To: Igor Mammedov <imammedo@redhat.com>
Cc: qemu-devel@nongnu.org, qemu-s390x@nongnu.org,
"Michael S . Tsirkin" <mst@redhat.com>,
Marcel Apfelbaum <marcel@redhat.com>,
Paolo Bonzini <pbonzini@redhat.com>,
Richard Henderson <rth@twiddle.net>,
Eduardo Habkost <ehabkost@redhat.com>,
David Gibson <david@gibson.dropbear.id.au>,
Markus Armbruster <armbru@redhat.com>,
qemu-ppc@nongnu.org, Pankaj Gupta <pagupta@redhat.com>,
Alexander Graf <agraf@suse.de>, Cornelia Huck <cohuck@redhat.com>,
Christian Borntraeger <borntraeger@de.ibm.com>,
Luiz Capitulino <lcapitulino@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v4 01/14] memory-device: drop assert related to align and start of address space
Date: Tue, 29 May 2018 18:02:06 +0200 [thread overview]
Message-ID: <cb69838b-e346-503c-f86d-9a0746c6c1e6@redhat.com> (raw)
In-Reply-To: <20180529152714.232f952c@redhat.com>
On 29.05.2018 15:27, Igor Mammedov wrote:
> On Thu, 17 May 2018 10:15:14 +0200
> David Hildenbrand <david@redhat.com> wrote:
>
>> The start of the address space does not have to be aligned for the
>> search. Handle this case explicitly when starting the search for a new
>> address.
> That's true,
> but commit message doesn't explain why address_space_start
> should be allowed to be non aligned.
>
> At least with this assert we would notice early that
> board allocating misaligned address space.
> I'd keep the assert unless there is a good reason to drop it.
That reason might be that I can easily crash QEMU
./x86_64-softmmu/qemu-system-x86_64 -m 256M,maxmem=20G,slots=2 -object
memory-backend-file,id=mem0,size=8192M,mem-path=/dev/zero,align=8192M
-device pc-dimm,id=dimm1,memdev=mem0
ERROR:hw/mem/memory-device.c:146:memory_device_get_free_addr: assertion
failed: (QEMU_ALIGN_UP(address_space_start, align) == address_space_start)
>
>
>>
>> Signed-off-by: David Hildenbrand <david@redhat.com>
>> ---
>> hw/mem/memory-device.c | 3 +--
>> 1 file changed, 1 insertion(+), 2 deletions(-)
>>
>> diff --git a/hw/mem/memory-device.c b/hw/mem/memory-device.c
>> index 3e04f3954e..361d38bfc5 100644
>> --- a/hw/mem/memory-device.c
>> +++ b/hw/mem/memory-device.c
>> @@ -116,7 +116,6 @@ uint64_t memory_device_get_free_addr(MachineState *ms, const uint64_t *hint,
>> address_space_start = ms->device_memory->base;
>> address_space_end = address_space_start +
>> memory_region_size(&ms->device_memory->mr);
>> - g_assert(QEMU_ALIGN_UP(address_space_start, align) == address_space_start);
>> g_assert(address_space_end >= address_space_start);
>>
>> memory_device_check_addable(ms, size, errp);
>> @@ -149,7 +148,7 @@ uint64_t memory_device_get_free_addr(MachineState *ms, const uint64_t *hint,
>> return 0;
>> }
>> } else {
>> - new_addr = address_space_start;
>> + new_addr = QEMU_ALIGN_UP(address_space_start, align);
>> }
>>
>> /* find address range that will fit new memory device */
>
--
Thanks,
David / dhildenb
next prev parent reply other threads:[~2018-05-29 16:02 UTC|newest]
Thread overview: 76+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-17 8:15 [Qemu-devel] [PATCH v4 00/14] MemoryDevice: use multi stage hotplug handlers David Hildenbrand
2018-05-17 8:15 ` [Qemu-devel] [PATCH v4 01/14] memory-device: drop assert related to align and start of address space David Hildenbrand
2018-05-29 13:27 ` Igor Mammedov
2018-05-29 16:02 ` David Hildenbrand [this message]
2018-05-30 12:57 ` Igor Mammedov
2018-05-30 14:06 ` David Hildenbrand
2018-05-31 13:54 ` Igor Mammedov
2018-06-04 10:53 ` David Hildenbrand
2018-06-07 13:26 ` Igor Mammedov
2018-06-07 14:12 ` David Hildenbrand
2018-05-17 8:15 ` [Qemu-devel] [PATCH v4 02/14] memory-device: introduce separate config option David Hildenbrand
2018-05-30 12:58 ` Igor Mammedov
2018-05-17 8:15 ` [Qemu-devel] [PATCH v4 03/14] qdev: let machine hotplug handler to override bus hotplug handler David Hildenbrand
2018-06-05 1:02 ` David Gibson
2018-05-17 8:15 ` [Qemu-devel] [PATCH v4 04/14] pc: prepare for multi stage hotplug handlers David Hildenbrand
2018-05-30 13:08 ` Igor Mammedov
2018-05-30 14:13 ` David Hildenbrand
2018-05-31 14:13 ` Igor Mammedov
2018-06-04 11:27 ` David Hildenbrand
2018-06-07 13:44 ` Igor Mammedov
2018-06-07 14:00 ` David Hildenbrand
2018-06-08 12:24 ` Igor Mammedov
2018-06-08 12:32 ` David Hildenbrand
2018-06-08 12:55 ` Michael S. Tsirkin
2018-06-08 13:07 ` David Hildenbrand
2018-06-08 15:12 ` Michael S. Tsirkin
2018-06-13 10:58 ` David Hildenbrand
2018-06-13 15:48 ` Igor Mammedov
2018-06-13 15:51 ` David Hildenbrand
2018-06-13 18:32 ` Michael S. Tsirkin
2018-06-13 19:37 ` David Hildenbrand
2018-06-13 22:05 ` Michael S. Tsirkin
2018-06-14 6:14 ` David Hildenbrand
2018-06-14 9:16 ` Igor Mammedov
2018-06-14 9:20 ` Igor Mammedov
2018-05-17 8:15 ` [Qemu-devel] [PATCH v4 05/14] pc: route all memory devices through the machine hotplug handler David Hildenbrand
2018-05-30 13:12 ` Igor Mammedov
2018-05-30 14:08 ` David Hildenbrand
2018-05-30 14:27 ` Paolo Bonzini
2018-05-30 14:31 ` David Hildenbrand
2018-05-17 8:15 ` [Qemu-devel] [PATCH v4 06/14] spapr: prepare for multi stage hotplug handlers David Hildenbrand
2018-05-17 12:43 ` [Qemu-devel] [Qemu-ppc] " Greg Kurz
2018-06-01 10:33 ` [Qemu-devel] " Igor Mammedov
2018-06-05 1:08 ` David Gibson
2018-06-05 7:51 ` David Hildenbrand
2018-06-07 14:26 ` Igor Mammedov
2018-05-17 8:15 ` [Qemu-devel] [PATCH v4 07/14] spapr: route all memory devices through the machine hotplug handler David Hildenbrand
2018-06-05 1:09 ` David Gibson
2018-06-05 7:51 ` David Hildenbrand
2018-05-17 8:15 ` [Qemu-devel] [PATCH v4 08/14] spapr: handle pc-dimm unplug via hotplug handler chain David Hildenbrand
2018-06-01 10:53 ` Igor Mammedov
2018-06-05 1:12 ` David Gibson
2018-05-17 8:15 ` [Qemu-devel] [PATCH v4 09/14] spapr: handle cpu core " David Hildenbrand
2018-06-01 10:57 ` Igor Mammedov
2018-06-05 1:13 ` David Gibson
2018-05-17 8:15 ` [Qemu-devel] [PATCH v4 10/14] memory-device: new functions to handle plug/unplug David Hildenbrand
2018-05-17 8:15 ` [Qemu-devel] [PATCH v4 11/14] pc-dimm: implement new memory device functions David Hildenbrand
2018-05-17 8:15 ` [Qemu-devel] [PATCH v4 12/14] memory-device: factor out pre-plug into hotplug handler David Hildenbrand
2018-06-01 11:17 ` Igor Mammedov
2018-06-04 11:45 ` David Hildenbrand
2018-06-07 15:00 ` Igor Mammedov
2018-06-07 15:10 ` David Hildenbrand
2018-05-17 8:15 ` [Qemu-devel] [PATCH v4 13/14] memory-device: factor out unplug " David Hildenbrand
2018-06-01 11:31 ` Igor Mammedov
2018-06-04 15:54 ` David Hildenbrand
2018-05-17 8:15 ` [Qemu-devel] [PATCH v4 14/14] memory-device: factor out plug " David Hildenbrand
2018-06-01 11:39 ` Igor Mammedov
2018-06-04 11:47 ` David Hildenbrand
2018-06-07 10:44 ` [Qemu-devel] [qemu-s390x] " David Hildenbrand
2018-05-25 12:43 ` [Qemu-devel] [qemu-s390x] [PATCH v4 00/14] MemoryDevice: use multi stage hotplug handlers David Hildenbrand
2018-05-30 14:03 ` Paolo Bonzini
2018-05-31 11:47 ` Igor Mammedov
2018-05-31 11:50 ` Paolo Bonzini
2018-06-01 12:13 ` Igor Mammedov
2018-06-04 10:03 ` David Hildenbrand
2018-06-08 9:57 ` David Hildenbrand
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=cb69838b-e346-503c-f86d-9a0746c6c1e6@redhat.com \
--to=david@redhat.com \
--cc=agraf@suse.de \
--cc=armbru@redhat.com \
--cc=borntraeger@de.ibm.com \
--cc=cohuck@redhat.com \
--cc=david@gibson.dropbear.id.au \
--cc=ehabkost@redhat.com \
--cc=imammedo@redhat.com \
--cc=lcapitulino@redhat.com \
--cc=marcel@redhat.com \
--cc=mst@redhat.com \
--cc=pagupta@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@nongnu.org \
--cc=qemu-s390x@nongnu.org \
--cc=rth@twiddle.net \
/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).