All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Michael S. Tsirkin" <mst@redhat.com>
To: Igor Mammedov <imammedo@redhat.com>
Cc: qemu-devel@nongnu.org, marcel.a@redhat.com
Subject: Re: [Qemu-devel] [PATCH 7/9] acpi: replace opencoded notify codes with named values
Date: Mon, 8 Dec 2014 22:54:03 +0200	[thread overview]
Message-ID: <20141208205403.GF29909@redhat.com> (raw)
In-Reply-To: <1418054888-11310-8-git-send-email-imammedo@redhat.com>

On Mon, Dec 08, 2014 at 04:08:06PM +0000, Igor Mammedov wrote:
> Signed-off-by: Igor Mammedov <imammedo@redhat.com>

I'm not sure this makes sense for these constants.

Device Check seems more readable than ACPI_DEV_CHK.
If your object here is readability, please do not
abbreviate.

Generally ability to match spec names exactly is
what made me prefer code comments to enums for one-off constants.
Looking up "Device Check" works in any spec version,
I don't have to dig up the exact one, find table by name,
break my eyes trying to locate the correct line in
a huge table.
Just text search, and the correct line is highlighted.

Why look in another spec version you might ask?
Well it's definitely helpful to understand legacy
guest quirks.


> ---
>  hw/i386/acpi-build.c             | 4 ++--
>  include/hw/acpi/acpi_gen_utils.h | 6 ++++++
>  2 files changed, 8 insertions(+), 2 deletions(-)
> 
> diff --git a/hw/i386/acpi-build.c b/hw/i386/acpi-build.c
> index 0f6202d..a33d130 100644
> --- a/hw/i386/acpi-build.c
> +++ b/hw/i386/acpi-build.c
> @@ -840,10 +840,10 @@ static void build_pci_bus_end(PCIBus *bus, void *bus_state)
>              build_append_namestring(method, "BNUM");
>              build_append_namestring(method, "DVNT");
>              build_append_namestring(method, "PCIU");
> -            build_append_int(method, 1); /* Device Check */
> +            build_append_int(method, ACPI_DEV_CHK);
>              build_append_namestring(method, "DVNT");
>              build_append_namestring(method, "PCID");
> -            build_append_int(method, 3); /* Eject Request */
> +            build_append_int(method, ACPI_DEV_EJ);
>          }
>  
>          /* Notify about child bus events in any case */
> diff --git a/include/hw/acpi/acpi_gen_utils.h b/include/hw/acpi/acpi_gen_utils.h
> index fd50625..ce76dc1 100644
> --- a/include/hw/acpi/acpi_gen_utils.h
> +++ b/include/hw/acpi/acpi_gen_utils.h
> @@ -5,6 +5,12 @@
>  #include <glib.h>
>  #include "qemu/compiler.h"
>  
> +/* ACPI 5.0: table "Device Object Notification Values" */
> +enum {
> +    ACPI_DEV_CHK = 1,
> +    ACPI_DEV_EJ = 3,
> +};
> +
>  GArray *build_alloc_array(void);
>  void build_free_array(GArray *array);
>  void build_prepend_byte(GArray *array, uint8_t val);
> -- 
> 1.8.3.1

  reply	other threads:[~2014-12-08 22:39 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-08 16:07 [Qemu-devel] [PATCH 0/9] pc: acpi: various fixes and cleanups Igor Mammedov
2014-12-08 16:08 ` [Qemu-devel] [PATCH 1/9] pc: acpi: fix WindowsXP BSOD when memory hotplug is enabled Igor Mammedov
2014-12-08 20:57   ` Michael S. Tsirkin
2014-12-09 10:05     ` Igor Mammedov
2014-12-09 10:33       ` Michael S. Tsirkin
2014-12-08 16:08 ` [Qemu-devel] [PATCH 2/9] pc: acpi: decribe bridge device as not hotpluggable Igor Mammedov
2014-12-08 19:13   ` Michael S. Tsirkin
2014-12-09 10:27     ` Igor Mammedov
2014-12-09 10:34       ` Michael S. Tsirkin
2014-12-09 11:45         ` Igor Mammedov
2014-12-09 12:51           ` Michael S. Tsirkin
2014-12-09 12:57             ` Igor Mammedov
2014-12-09 13:16               ` Michael S. Tsirkin
2014-12-09 13:08             ` Igor Mammedov
2014-12-08 16:08 ` [Qemu-devel] [PATCH 3/9] pc: acpi-build: cleanup AcpiPmInfo initialization Igor Mammedov
2014-12-08 21:03   ` Michael S. Tsirkin
2014-12-09 10:29     ` Igor Mammedov
2014-12-08 16:08 ` [Qemu-devel] [PATCH 4/9] acpi: build_append_nameseg(): add padding if necessary Igor Mammedov
2014-12-08 21:15   ` Michael S. Tsirkin
2014-12-09 10:32     ` Igor Mammedov
2014-12-09 10:38       ` Michael S. Tsirkin
2014-12-09 12:55         ` Igor Mammedov
2014-12-08 16:08 ` [Qemu-devel] [PATCH 5/9] acpi: move generic aml building helpers into dedictated file Igor Mammedov
2014-12-08 20:43   ` Michael S. Tsirkin
2014-12-09 10:37     ` Igor Mammedov
2014-12-08 16:08 ` [Qemu-devel] [PATCH 6/9] acpi: add build_append_namestring() helper Igor Mammedov
2014-12-08 20:21   ` Michael S. Tsirkin
2014-12-09 10:39     ` Igor Mammedov
2014-12-09 12:02       ` Michael S. Tsirkin
2014-12-09 12:59         ` Igor Mammedov
2014-12-08 16:08 ` [Qemu-devel] [PATCH 7/9] acpi: replace opencoded notify codes with named values Igor Mammedov
2014-12-08 20:54   ` Michael S. Tsirkin [this message]
2014-12-09 10:59     ` Igor Mammedov
2014-12-08 16:08 ` [Qemu-devel] [PATCH 8/9] acpi: drop min-bytes in build_package() Igor Mammedov
2014-12-08 16:08 ` [Qemu-devel] [PATCH 9/9] pc: acpi-build: replace recursive PCI bus tree generation with loop based Igor Mammedov
2014-12-08 20:43   ` Michael S. Tsirkin
2014-12-09 14:01     ` Igor Mammedov
2014-12-09 14:29       ` Michael S. Tsirkin
2014-12-11 11:09         ` [Qemu-devel] [PATCH V2 9/9] pc: acpi-build: simplify PCI bus tree generation Igor Mammedov
2014-12-08 20:43 ` [Qemu-devel] [PATCH 0/9] pc: acpi: various fixes and cleanups Michael S. Tsirkin

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=20141208205403.GF29909@redhat.com \
    --to=mst@redhat.com \
    --cc=imammedo@redhat.com \
    --cc=marcel.a@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.