qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Amos Kong <akong@redhat.com>
To: "Gonglei (Arei)" <arei.gonglei@huawei.com>
Cc: "chenliang (T)" <chenliang88@huawei.com>,
	"Huangweidong (C)" <weidong.huang@huawei.com>,
	"peter.maydell@linaro.org" <peter.maydell@linaro.org>,
	"aik@ozlabs.ru" <aik@ozlabs.ru>,
	"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
	"agraf@suse.de" <agraf@suse.de>,
	"kraxel@redhat.com" <kraxel@redhat.com>,
	"dmitry@daynix.com" <dmitry@daynix.com>,
	"mst@redhat.com" <mst@redhat.com>,
	"armbru@redhat.com" <armbru@redhat.com>,
	"lersek@redhat.com" <lersek@redhat.com>,
	"marcel.a@redhat.com" <marcel.a@redhat.com>,
	"somlo@cmu.edu" <somlo@cmu.edu>,
	Luonengjun <luonengjun@huawei.com>,
	"Huangpeng (Peter)" <peter.huangpeng@huawei.com>,
	"alex.williamson@redhat.com" <alex.williamson@redhat.com>,
	"stefanha@redhat.com" <stefanha@redhat.com>,
	"pbonzini@redhat.com" <pbonzini@redhat.com>,
	"lcapitulino@redhat.com" <lcapitulino@redhat.com>,
	"rth@twiddle.net" <rth@twiddle.net>,
	"kwolf@redhat.com" <kwolf@redhat.com>,
	"peter.crosthwaite@xilinx.com" <peter.crosthwaite@xilinx.com>,
	"imammedo@redhat.com" <imammedo@redhat.com>,
	"afaerber@suse.de" <afaerber@suse.de>
Subject: Re: [Qemu-devel] [RFC PATCH 1/5] bootindex: add *_boot_device_path function
Date: Tue, 8 Jul 2014 22:55:12 +0800	[thread overview]
Message-ID: <20140708145512.GA3061@z.redhat.com> (raw)
In-Reply-To: <33183CC9F5247A488A2544077AF1902086C19408@SZXEMA503-MBS.china.huawei.com>

On Tue, Jul 08, 2014 at 01:22:53PM +0000, Gonglei (Arei) wrote:
> > -----Original Message-----
> > From: chenliang (T)
> > Sent: Tuesday, July 08, 2014 7:03 PM
> > To: Amos Kong
> > Cc: Gonglei (Arei); qemu-devel@nongnu.org; afaerber@suse.de;
> > agraf@suse.de; stefanha@redhat.com; aik@ozlabs.ru;
> > alex.williamson@redhat.com; armbru@redhat.com; eblake@redhat.com;
> > kwolf@redhat.com; peter.maydell@linaro.org; lcapitulino@redhat.com;
> > mst@redhat.com; pbonzini@redhat.com; lersek@redhat.com;
> > kraxel@redhat.com; imammedo@redhat.com; dmitry@daynix.com;
> > marcel.a@redhat.com; peter.crosthwaite@xilinx.com; rth@twiddle.net;
> > somlo@cmu.edu; Huangweidong (C); Luonengjun; Huangpeng (Peter)
> > Subject: Re: [RFC PATCH 1/5] bootindex: add *_boot_device_path function
> > 
> > On 2014/7/8 16:33, Amos Kong wrote:
> > 
> > > On Mon, Jul 07, 2014 at 05:10:57PM +0800, arei.gonglei@huawei.com
> > wrote:
> > >> From: Chenliang <chenliang88@huawei.com>
> > >>
> > >> Add del_boot_device_path and modify_boot_device_path. Device should
> > >> be removed from boot device list  by del_boot_device_path when device
> > >> hotplug. modify_boot_device_path is used to modify deviceboot order.
> > >
> > > s/hotplug/is unhotplugged/
> > >
> > > same issue in commitlog of patch 3/5
> > >
> 
> Yep, thanks!
> 
> > >> Signed-off-by: Chenliang <chenliang88@huawei.com>
> > >> Signed-off-by: Gonglei <arei.gonglei@huawei.com>
> > >> ---
> > >>  include/sysemu/sysemu.h |  4 ++++
> > >>  vl.c                    | 55
> > +++++++++++++++++++++++++++++++++++++++++++++++++
> > >>  2 files changed, 59 insertions(+)
> > >>
> > >> diff --git a/include/sysemu/sysemu.h b/include/sysemu/sysemu.h
> > >> index 285c45b..38ef1cd 100644
> > >> --- a/include/sysemu/sysemu.h
> > >> +++ b/include/sysemu/sysemu.h
> > >> @@ -204,6 +204,10 @@ void usb_info(Monitor *mon, const QDict *qdict);
> > >>
> > >>  void add_boot_device_path(int32_t bootindex, DeviceState *dev,
> > >>                            const char *suffix);
> > >> +void del_boot_device_path(int32_t bootindex, DeviceState *dev,
> > >> +                          const char *suffix);
> > >> +void modify_boot_device_path(int32_t bootindex, DeviceState *dev,
> > >> +                             const char *suffix);
> > >>  char *get_boot_devices_list(size_t *size, bool ignore_suffixes);
> > >>
> > >>  DeviceState *get_boot_device(uint32_t position);
> > >> diff --git a/vl.c b/vl.c
> > >> index a1686ef..6264e11 100644
> > >> --- a/vl.c
> > >> +++ b/vl.c
> > >> @@ -1247,6 +1247,61 @@ void add_boot_device_path(int32_t bootindex,
> > DeviceState *dev,
> > >>      QTAILQ_INSERT_TAIL(&fw_boot_order, node, link);
> > >>  }
> > >>
> > >> +static bool is_same_fw_dev_path(DeviceState *src, DeviceState *target)
> > >> +{
> > >> +    bool ret = false;
> > >> +    char *devpath_src = qdev_get_fw_dev_path(src);
> > >> +    char *devpath_target = qdev_get_fw_dev_path(target);
> > >> +
> > >> +    if (!strcmp(devpath_src, devpath_target)) {
> > >> +        ret = true;
> > >> +    }
> > >> +
> > >> +    g_free(devpath_src);
> > >> +    g_free(devpath_target);
> > >> +    return ret;
> > >> +}
> > >> +
> > >> +void del_boot_device_path(int32_t bootindex, DeviceState *dev,
> > >> +                          const char *suffix)
> > >> +{
> > >> +    FWBootEntry *i;
> > >> +
> > >> +    assert(dev != NULL);
> > >> +
> > >
> > > assert(booindex >= 0 || suffix != NULL);
> > >
> 
> suffix call be NULL. 
> 
> > >> +    QTAILQ_FOREACH(i, &fw_boot_order, link) {
> > >> +        if (is_same_fw_dev_path(i->dev, dev)) {
> > >
> > >                if (!suffix) {
> > >                    break;
> > >                }

If suffix is NULL, at least we should do nothing in the loop.

> > >
> > >> +            if (suffix && i->suffix && strcmp(i->suffix, suffix)) {
> > >> +                continue;
> > >> +            }

How about this one?

                   if (!suffix) {
                        break;
                   } else (i->suffix && strcmp(i->suffix, suffix)) {
                        continue;
                   }


> > >
> > > If suffix is NULL, then all the entries will be removed?
> 
> If suffix is NULL, the entry will be checked by the bootindex as below
> QTAILQ_FOREACH loop. If suffix and bootindex are all not match,
> no entry will not be deleted from the global fw_boot_order list.

This is why I added "assert(booindex >= 0 || suffix != NULL);" on
above.
                                         ^^^^
> > 
> > 
> > yes, it will be if caller don't give suffix.
> > 
> > >
> > >> +            QTAILQ_REMOVE(&fw_boot_order, i, link);
> > >> +            g_free(i->suffix);
> > >> +            g_free(i);
> > >> +            break;
> > >> +        }
> > >> +    }
> > >> +
> > >> +    if (bootindex == -1) {
> > >
> > >    if (bootindex < 0) {
> > 
> > 
> > acked
> > 
> > >
> > >> +        return;
> > >> +    }
> > >> +
> > >> +    QTAILQ_FOREACH(i, &fw_boot_order, link) {
> > >> +        if (i->bootindex == bootindex) {
> > >> +            QTAILQ_REMOVE(&fw_boot_order, i, link);
> > >> +            g_free(i->suffix);
> > >> +            g_free(i);
> > >> +            break;
> > >> +        }
> > >> +    }
> > >> +}
> > >> +
> > >> +void modify_boot_device_path(int32_t bootindex, DeviceState *dev,
> > >> +                             const char *suffix)
> > >> +{
> > >> +    del_boot_device_path(bootindex, dev, suffix);
> > >> +    add_boot_device_path(bootindex, dev, suffix);
> > >
> > > Why do you directly modify existed entry?
> > 
> > 
> > Sometimes, in old boot device list:
> > 
> > device_id      bootindex
> > net0           1
> > net1           2
> > net2           3
> > 
> > we want to make vm reboot from net2, we can do it like this:
> > 
> > modify_boot_device_path(bootindex=1, DeviceState=net2, suffix=NULL), the
> > new boot device list will like this:
> > 
> > device_id     bootindex
> > net2          1
> > net1          2
> > 
> 
> Yes. 
> the visual bootindex of net0 will be deleted, and then we can look 
> it as default value.
> 
> Best regards,
> -Gonglei

-- 
			Amos.

  reply	other threads:[~2014-07-08 14:55 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-07  9:10 [Qemu-devel] [RFC PATCH 0/5] modify boot order when vm is running arei.gonglei
2014-07-07  9:10 ` [Qemu-devel] [RFC PATCH 1/5] bootindex: add *_boot_device_path function arei.gonglei
2014-07-08  8:33   ` Amos Kong
2014-07-08 11:02     ` ChenLiang
2014-07-08 13:22       ` Gonglei (Arei)
2014-07-08 14:55         ` Amos Kong [this message]
2014-07-09  1:03           ` Gonglei (Arei)
2014-07-07  9:10 ` [Qemu-devel] [RFC PATCH 2/5] bootindex: reset bootindex when vm reset arei.gonglei
2014-07-07  9:10 ` [Qemu-devel] [RFC PATCH 3/5] bootindex: delete boot index when device is removed arei.gonglei
2014-07-07  9:11 ` [Qemu-devel] [RFC PATCH 4/5] bootindex: add qmp to set boot index when vm is running arei.gonglei
2014-07-07  9:11 ` [Qemu-devel] [RFC PATCH 5/5] bootindex: fix memory leak when set boot index arei.gonglei
2014-07-07  9:29 ` [Qemu-devel] [RFC PATCH 0/5] modify boot order when vm is running Michael S. Tsirkin
2014-07-07 10:03   ` Laszlo Ersek
2014-07-07 11:12     ` Gonglei (Arei)
2014-07-07 14:40       ` Laszlo Ersek
2014-07-08  0:54         ` Gonglei (Arei)
2014-07-07 11:08   ` Gonglei (Arei)
2014-07-07 13:07     ` Michael S. Tsirkin
2014-07-08  1:06       ` Gonglei (Arei)

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=20140708145512.GA3061@z.redhat.com \
    --to=akong@redhat.com \
    --cc=afaerber@suse.de \
    --cc=agraf@suse.de \
    --cc=aik@ozlabs.ru \
    --cc=alex.williamson@redhat.com \
    --cc=arei.gonglei@huawei.com \
    --cc=armbru@redhat.com \
    --cc=chenliang88@huawei.com \
    --cc=dmitry@daynix.com \
    --cc=imammedo@redhat.com \
    --cc=kraxel@redhat.com \
    --cc=kwolf@redhat.com \
    --cc=lcapitulino@redhat.com \
    --cc=lersek@redhat.com \
    --cc=luonengjun@huawei.com \
    --cc=marcel.a@redhat.com \
    --cc=mst@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=peter.crosthwaite@xilinx.com \
    --cc=peter.huangpeng@huawei.com \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=rth@twiddle.net \
    --cc=somlo@cmu.edu \
    --cc=stefanha@redhat.com \
    --cc=weidong.huang@huawei.com \
    /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).