From: Alexander Barabash <alexander_barabash@mentor.com>
To: "Andreas Färber" <afaerber@suse.de>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 1/1] Added address_space_init2().
Date: Tue, 8 Jan 2013 12:53:15 +0200	[thread overview]
Message-ID: <50EBFA9B.1010701@mentor.com> (raw)
In-Reply-To: <50EAC810.2060201@suse.de>
Hi,
On 01/07/2013 03:05 PM, Andreas Färber wrote:
> A "memory: " prefix in the subject would've been nice for filtering.
OK
>
> Am 07.01.2013 13:07, schrieb Alexander Barabash:
>> address_space_init2: initializes a named address space.
> What for? There are no users in this patch that justify its utility over
> setting the field manually.
Names of memory regions and address spaces are used for debugging purposes.
Currently, there is no way for address spaces other than "memory" and 
"io" to
appear in debugging output.
This is used in some code to be posted later.
>
> The name is really awful, maybe ..._init_with_name or add a name
> argument to the existing function and let the existing callers pass NULL?
Changing the existing callers of address_space_init() is OK with me.
I did not do that primarily because that would be an obvious way to do
to start with. And since this was not implemented this way,
there should have been some some reason.
However, I'll send a PATCH along these lines.
>
> Regards,
> Andreas
Regards,
Alex
>
>> Signed-off-by: Alexander Barabash <alexander_barabash@mentor.com>
>> ---
>>   include/exec/memory.h |    9 +++++++++
>>   memory.c              |    6 ++++++
>>   2 files changed, 15 insertions(+)
>>
>> diff --git a/include/exec/memory.h b/include/exec/memory.h
>> index 2322732..8f8a31d 100644
>> --- a/include/exec/memory.h
>> +++ b/include/exec/memory.h
>> @@ -820,6 +820,15 @@ void mtree_info(fprintf_function mon_printf, void *f);
>>    */
>>   void address_space_init(AddressSpace *as, MemoryRegion *root);
>>   
>> +/**
>> + * address_space_init2: initializes a named address space
>> + *
>> + * @as: an uninitialized #AddressSpace
>> + * @root: a #MemoryRegion that routes addesses for the address space
>> + * @name: used for debugging
>> + */
>> +void address_space_init2(AddressSpace *as, MemoryRegion *root,
>> +                         const char *name);
>>   
>>   /**
>>    * address_space_destroy: destroy an address space
>> diff --git a/memory.c b/memory.c
>> index 410c5f8..1652c10 100644
>> --- a/memory.c
>> +++ b/memory.c
>> @@ -1574,6 +1574,12 @@ void address_space_init(AddressSpace *as, MemoryRegion *root)
>>       address_space_init_dispatch(as);
>>   }
>>   
>> +void address_space_init2(AddressSpace *as, MemoryRegion *root, const char *name)
>> +{
>> +    address_space_init(as, root);
>> +    as->name = g_strdup(name);
>> +}
>> +
>>   void address_space_destroy(AddressSpace *as)
>>   {
>>       /* Flush out anything from MemoryListeners listening in on this */
next prev parent reply	other threads:[~2013-01-08 10:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-07 12:07 [Qemu-devel] [PATCH 1/1] Added address_space_init2() Alexander Barabash
2013-01-07 13:05 ` Andreas Färber
2013-01-08 10:53   ` Alexander Barabash [this message]
2013-01-08 11:22 ` [Qemu-devel] [PATCH 1/1] memory: add name in AddressSpace initialization Alexander Barabash
2013-01-08 14:00   ` Anthony Liguori
2013-01-08 18:28     ` Alexander Barabash
2013-01-08 19:18     ` [Qemu-devel] [PATCH v3 " Alexander Barabash
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=50EBFA9B.1010701@mentor.com \
    --to=alexander_barabash@mentor.com \
    --cc=afaerber@suse.de \
    --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).