qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Gonglei <arei.gonglei@huawei.com>
To: "Gonglei (Arei)" <arei.gonglei@huawei.com>
Cc: "pbonzini@redhat.com" <pbonzini@redhat.com>,
	"mst@redhat.com" <mst@redhat.com>,
	"Huangweidong (C)" <weidong.huang@huawei.com>,
	"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
	"Huangpeng (Peter)" <peter.huangpeng@huawei.com>
Subject: Re: [Qemu-devel] [PATCH 0/5] bootdevice: Refactor and improvement
Date: Thu, 11 Dec 2014 16:29:41 +0800	[thread overview]
Message-ID: <548955F5.1080901@huawei.com> (raw)
In-Reply-To: <1417691986-948-1-git-send-email-arei.gonglei@huawei.com>

On 2014/12/4 19:19, Gonglei (Arei) wrote:

> From: Gonglei <arei.gonglei@huawei.com>
> 
> Patch 1 just move boot order related code to bootdevice.c.
> Patch 2,3,5 add an argument to corresponding functions.
> This way, we can propagate the error messages to the caller.
> Maybe somebody will say we will remove the legacy boot order
> in the future, instead of using bootindex. But at present,
> for PPC, the have no way support bootindex, ARM on the flight
> (Laszlo Ersek) as far as know.
> 
> After this work, we can easily to add QMP command for existing
> HMP command 'boot_set' if we have a requirement.
> 
> Gonglei (5):
>   bootdevice: move code about bootorder from vl.c to bootdevice.c
>   bootdevice: add Error **errp argument for validate_bootdevices()
>   bootdevice: add Error **errp argument for qemu_boot_set()
>   bootdevice: add validate check for qemu_boot_set()
>   bootdevice: add Error **errp argument for QEMUBootSetHandler
> 
>  bootdevice.c            | 73 ++++++++++++++++++++++++++++++++++++++++++++++
>  hw/i386/pc.c            | 21 ++++++--------
>  hw/ppc/mac_newworld.c   |  4 +--
>  hw/ppc/mac_oldworld.c   |  5 ++--
>  hw/sparc/sun4m.c        |  4 +--
>  hw/sparc64/sun4u.c      |  4 +--
>  include/hw/hw.h         |  6 ----
>  include/sysemu/sysemu.h |  7 +++++
>  monitor.c               | 14 ++++-----
>  vl.c                    | 77 +++++++++----------------------------------------
>  10 files changed, 116 insertions(+), 99 deletions(-)
> 

Any comments and/or Acks will be appreciated.
Then I'll send a pull request if no one is against  this :)

Regards,
-Gonglei

      parent reply	other threads:[~2014-12-11  8:32 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-04 11:19 [Qemu-devel] [PATCH 0/5] bootdevice: Refactor and improvement arei.gonglei
2014-12-04 11:19 ` [Qemu-devel] [PATCH 1/5] bootdevice: move code about bootorder from vl.c to bootdevice.c arei.gonglei
2014-12-04 11:19 ` [Qemu-devel] [PATCH 2/5] bootdevice: add Error **errp argument for validate_bootdevices() arei.gonglei
2014-12-04 11:19 ` [Qemu-devel] [PATCH 3/5] bootdevice: add Error **errp argument for qemu_boot_set() arei.gonglei
2014-12-04 11:19 ` [Qemu-devel] [PATCH 4/5] bootdevice: add validate check " arei.gonglei
2014-12-04 11:19 ` [Qemu-devel] [PATCH 5/5] bootdevice: add Error **errp argument for QEMUBootSetHandler arei.gonglei
2014-12-11  8:29 ` Gonglei [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=548955F5.1080901@huawei.com \
    --to=arei.gonglei@huawei.com \
    --cc=mst@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=peter.huangpeng@huawei.com \
    --cc=qemu-devel@nongnu.org \
    --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).