[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] [PATCH V3 0/6] firmware changes as part of QEMU/Xen merge.


  • To: Pasi Kärkkäinen <pasik@xxxxxx>, <anthony.perard@xxxxxxxxxx>
  • From: Keir Fraser <keir@xxxxxxx>
  • Date: Fri, 29 Oct 2010 14:18:29 +0100
  • Cc: Xen Devel <xen-devel@xxxxxxxxxxxxxxxxxxx>
  • Delivery-date: Fri, 29 Oct 2010 06:19:14 -0700
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=sender:user-agent:date:subject:from:to:cc:message-id:thread-topic :thread-index:in-reply-to:mime-version:content-type :content-transfer-encoding; b=C1J64fJaSMkGF95nRYIDgQhp1Q8AyOcKOoRLt8AentLpK2N+ufeoPytcX8sC5f+ijn EKR7AeF35K0AyPGVY6kXMVO1Qmhap6zeDru00PUXC52f6e/K9EmFIUnRGCeg8tmoQKQ3 WG/wrhSKaoM3cibMQa+tAjaanDNsY/XpWsSLM=
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>
  • Thread-index: Act3a49THOaYcsqpC0GM7xzz66hu+AAADdve
  • Thread-topic: [Xen-devel] [PATCH V3 0/6] firmware changes as part of QEMU/Xen merge.

On 29/10/2010 14:16, "Keir Fraser" <keir@xxxxxxx> wrote:

>> Should it be called something else than HVM_PARAM_ACPI_NEW_IOPORT ?
>> After a couple of years "NEW" might not make much sense anymore..
>> 
>> IOPORT_V2 ? Or something..
> 
> I've asked for a nice big explanatory comment to be added beside the
> parameter's definition. Also we should treat this field as a version number,
> so baking a fixed version into its name is not a good idea. With the
> explanatory comment, I think its existing name is good enough. To do much
> better the name would have to become cumbersomely long.

That said, HVM_PARAM_ACPI_IOPORTS_LOCATION might be better... I'm not
personally that fussed either way however.

 -- Keir



_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.