qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: zhanghailiang <zhang.zhanghailiang@huawei.com>
To: Michael Roth <mdroth@linux.vnet.ibm.com>, qemu-devel@nongnu.org
Cc: hangaohuai@huawei.com, peter.huangpeng@huawei.com
Subject: Re: [Qemu-devel] [PATCH RFC for-2.3 3/6] qga: implement qmp_guest_get_memory_blocks() for Linux with sysfs
Date: Mon, 22 Dec 2014 18:13:36 +0800	[thread overview]
Message-ID: <5497EED0.7070205@huawei.com> (raw)
In-Reply-To: <20141221211734.15420.72276@loki>

On 2014/12/22 5:17, Michael Roth wrote:
> Quoting zhanghailiang (2014-12-06 00:59:16)
>> We can get guest's memory block information by using command
>> "guest-get-memory-blocks", the returned value contains a list of memory block
>> info, such as phys_index, online state, can-offline info.
>>
>> Signed-off-by: zhanghailiang <zhang.zhanghailiang@huawei.com>
>> ---
>>   qga/commands-posix.c | 66 +++++++++++++++++++++++++++++++++++++++++++++++-----
>>   1 file changed, 60 insertions(+), 6 deletions(-)
>>
>> diff --git a/qga/commands-posix.c b/qga/commands-posix.c
>> index 8917dca..d3f7d4f 100644
>> --- a/qga/commands-posix.c
>> +++ b/qga/commands-posix.c
>> @@ -2005,6 +2005,60 @@ static void transfer_memory_block(GuestMemoryBlock *mem_blk, bool sys2memblk,
>>       g_assert(res == 0);
>>   }
>>
>> +GuestMemoryBlockList *qmp_guest_get_memory_blocks(Error **errp)
>> +{
>> +    GuestMemoryBlockList *head, **link;
>> +    Error *local_err = NULL;
>> +    struct dirent *de;
>> +    DIR *dp;
>> +
>> +    head = NULL;
>> +    link = &head;
>> +
>> +    dp = opendir("/sys/devices/system/memory/");
>> +    if (!dp) {
>> +        error_setg_errno(errp, errno, "Can't open directory"
>> +                         "\"/sys/devices/system/memory/\"\n");
>> +        return NULL;
>> +    }
>> +
>> +    /* Note: the phys_index of memory block may be discontinuous,
>> +     * this is because a memblk is the unit of the Sparse Memory design, which
>> +     * allows discontinuous memory ranges (ex. NUMA), so here we should
>> +     * traverse the memory block directory.
>> +     */
>> +    while ((de = readdir(dp)) != NULL) {
>> +        GuestMemoryBlock *mem_blk;
>> +        GuestMemoryBlockList *entry;
>> +
>> +        if ((strncmp(de->d_name, "memory", 6) != 0) ||
>> +            !(de->d_type & DT_DIR)) {
>> +            continue;
>> +        }
>> +
>> +        mem_blk = g_malloc0(sizeof *mem_blk);
>> +        /* The d_name is "memoryXXX",  phys_index is block id, same as XXX */
>> +        mem_blk->phys_index = strtoul(&de->d_name[6], NULL, 10);
>> +        mem_blk->has_can_offline = true; /* lolspeak ftw */
>
> My initial thought as well :P
>

Ha, yes. ;)

>> +        transfer_memory_block(mem_blk, true, &local_err);
>> +
>> +        entry = g_malloc0(sizeof *entry);
>> +        entry->value = mem_blk;
>> +
>> +        *link = entry;
>> +        link = &entry->next;
>> +    }
>> +
>> +    if (local_err == NULL) {
>> +        /* there's no guest with zero memroy blocks */
>
> typo
>
>> +        g_assert(head != NULL);
>
> As commented on in earlier patches, guest errors shouldnt crash the guest agent
> if it can be avoided.
>

OK.

>> +        return head;
>> +    }
>> +
>> +    qapi_free_GuestMemoryBlockList(head);
>> +    error_propagate(errp, local_err);
>> +    return NULL;
>> +}
>>   #else /* defined(__linux__) */
>>
>>   void qmp_guest_suspend_disk(Error **errp)
>> @@ -2040,6 +2094,12 @@ int64_t qmp_guest_set_vcpus(GuestLogicalProcessorList *vcpus, Error **errp)
>>       return -1;
>>   }
>>
>> +GuestMemoryBlockList *qmp_guest_get_memory_blocks(Error **errp)
>> +{
>> +    error_set(errp, QERR_UNSUPPORTED);
>> +    return NULL;
>> +}
>> +
>>   #endif
>>
>>   #if !defined(CONFIG_FSFREEZE)
>> @@ -2126,12 +2186,6 @@ GList *ga_command_blacklist_init(GList *blacklist)
>>       return blacklist;
>>   }
>>
>> -GuestMemoryBlockList *qmp_guest_get_memory_blocks(Error **errp)
>> -{
>> -    error_set(errp, QERR_UNSUPPORTED);
>> -    return NULL;
>> -}
>> -
>
> Looks like some unecessary code movement made it's way into the patch. Please
> squash this change into original patch
>

OK, will fix that. Thanks.

>>   int64_t qmp_guest_set_memory_blocks(GuestMemoryBlockList *mem_blks,
>>                                       Error **errp)
>>   {
>> --
>> 1.7.12.4
>
>
> .
>

  reply	other threads:[~2014-12-22 10:14 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-06  6:59 [Qemu-devel] [PATCH RFC for-2.3 0/6] qga: add three logical memory hotplug related commands zhanghailiang
2014-12-06  6:59 ` [Qemu-devel] [PATCH RFC for-2.3 1/6] qga: introduce three guest memory block commands with stubs zhanghailiang
2014-12-21 20:10   ` Michael Roth
2014-12-22 10:02     ` zhanghailiang
2014-12-06  6:59 ` [Qemu-devel] [PATCH RFC for-2.3 2/6] qga: introduce three help functions for memory block functions zhanghailiang
2014-12-21 20:58   ` Michael Roth
2014-12-22 10:12     ` zhanghailiang
2014-12-06  6:59 ` [Qemu-devel] [PATCH RFC for-2.3 3/6] qga: implement qmp_guest_get_memory_blocks() for Linux with sysfs zhanghailiang
2014-12-21 21:17   ` Michael Roth
2014-12-22 10:13     ` zhanghailiang [this message]
2014-12-06  6:59 ` [Qemu-devel] [PATCH RFC for-2.3 4/6] qga: implement qmp_guest_set_memory_blocks() " zhanghailiang
2014-12-21 21:23   ` Michael Roth
2014-12-22 10:20     ` zhanghailiang
2014-12-06  6:59 ` [Qemu-devel] [PATCH RFC for-2.3 5/6] qga: implement qmp_guest_get_memory_block_size() " zhanghailiang
2014-12-21 21:41   ` Michael Roth
2014-12-22 10:21     ` zhanghailiang
2014-12-06  6:59 ` [Qemu-devel] [PATCH RFC for-2.3 6/6] qga: add memory block command that unsupported to blacklist zhanghailiang
2014-12-21 21:45   ` Michael Roth
2014-12-11 10:16 ` [Qemu-devel] [PATCH RFC for-2.3 0/6] qga: add three logical memory hotplug related commands zhanghailiang
2014-12-17  9:22 ` zhanghailiang

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=5497EED0.7070205@huawei.com \
    --to=zhang.zhanghailiang@huawei.com \
    --cc=hangaohuai@huawei.com \
    --cc=mdroth@linux.vnet.ibm.com \
    --cc=peter.huangpeng@huawei.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).