All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ross Philipson <ross.philipson@citrix.com>
To: Art Napor <artnapor@yahoo.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: HVM firmware passthrough - helper library
Date: Mon, 1 Apr 2013 18:04:48 -0400	[thread overview]
Message-ID: <515A0480.5000407@citrix.com> (raw)
In-Reply-To: <1364359855.76582.YahooMailNeo@web161404.mail.bf1.yahoo.com>

On 03/27/2013 12:50 AM, Art Napor wrote:
> Works great with the updated libxl commits - thanks.
>
>  > ./biospt 6
>  > Make SMBIOS file from FW.
>  > Fail(1), errno: 2
>
> Looks like this does require the sysfs-dmi kmod to expose the dmi
> structure for the utility to write out the smbios_fw.bin.
>
> # ./biospt 6
> Make SMBIOS file from FW.
> Make SMBIOS Xen vendor struct.
> Wrote SMBIOS structures file: smbios_fw.bin count: 8
> Make ACPI SLIC file from FW.
> Fail(3), errno: 2
>
> Do the ACPI tables require the same exposure via sysfs? Not sure if this
> changes from 2.6 to 3.x kernels. The biospt utility can dump the ACPI
> tables using the MMAP option, but not via sysfs on a 3.4.32 system.

They are in the same place on my wheezy with 3.2.x kernel. I would be 
pretty surprised if they moved. Can you go in to 
/sys/firmware/acpi/tables and see what's there? Maybe try a hexdump -C < 
SLIC ...

>
>
> Thanks,
> Art
>
>
> ------------------------------------------------------------------------
> *From:* Ross Philipson <ross.philipson@citrix.com>
> *To:* Art Napor <artnapor@yahoo.com>; "xen-devel@lists.xensource.com"
> <xen-devel@lists.xensource.com>
> *Sent:* Sunday, March 24, 2013 5:10 PM
> *Subject:* Re: HVM firmware passthrough - helper library
>
> On 03/21/2013 03:42 PM, Art Napor wrote:
>  > Ross,
>  >
>  > I rebuilt Xen 4.2.1 with the V5 patch series and the updated helper
>  > library. The biospt utility built cleanly and runs on Dom0 with the
>  > aformentioned libraries in place. However, I'm not seeing the SMBIOS
>  > strings passed through to the DomU (A Centos 5 VM). Options 1 and 3
>  > using the biostpt utility appear to dump the SMBIOS and ACPI tables, but
>  > I'm not sure how to pass the tables in to the VM?
>
> Look at the related commits to libxl. After the firmware chunks are
> given to libxc to load into the new domain, the addresses are returned
> to libxl which writes them to xenstore.
>
>  >
>  > [root@localhost biospt]# ./biospt
>  > Usage:
>  > $ biospt <n>
>  > 1 - Write some SMBIOS tables using MMAP
>  > 2 - Write some SMBIOS tables using SYSFS
>  > 3 - Write some ACPI tables using MMAP
>  > 4 - Write some ACPI using SYSFS
>  > 5 - Read and trace DMI files
>  > 6 - Write out some test files
>  >
>  > ./biospt 6
>  > Make SMBIOS file from FW.
>  > Fail(1), errno: 2
>
> This is a rather rough test app for using the library. You should look
> closely at the code in it and figure out what it is doing. It does not
> have very robust error handling etc.
>
> Thanks
> Ross
>
>  >
>  >
>  > -
>  > Art
>  >
>  > ------------------------------------------------------------------------
>  > *From:* Ross Philipson <ross.philipson@citrix.com
> <mailto:ross.philipson@citrix.com>>
>  > *To:* xen-devel@lists.xensource.com
> <mailto:xen-devel@lists.xensource.com>
>  > *Cc:* Art Napor <artnapor@yahoo.com <mailto:artnapor@yahoo.com>>
>  > *Sent:* Wednesday, March 20, 2013 4:08 PM
>  > *Subject:* Re: HVM firmware passthrough - helper library
>  >
>  >
>  > > Ross,
>  > >
>  > > Finally got back to this project to test out the helper lib using
> the v3
>  > > hvm-firmware passthrough patches with Xen 4.2.1. When building from
>  > > tools/firmware the build failed with the following output:
>  > >
>  > > make
>  > > gcc -Wl,-soname -Wl,libxenhvm.so.1.0 -shared -o libxenhvm.so.1.0.0
>  > > xenhvm.opic smbios_module.opic acpi_module.opic xh_internal.opic
>  > >
>  >
> /home/ajn131/rpmbuild/SOURCES/xen-4.2.1/tools/firmware/libhvm/../../../tools/xenstore/libxenstore.so
>  > >
>  > > xenhvm.opic: could not read symbols: File in wrong format
>  > > collect2: ld returned 1 exit status
>  > > make: *** [libxenhvm.so.1.0.0] Error 1
>  > >
>  > > I was hoping to integrate the build into the RPM. Any thoughts?
> Should I
>  > > try it with the latest 4.3?
>  > >
>  > >
>  > > Thanks Again,
>  > >
>  > > -
>  > > Art
>  >
>  > Art,
>  >
>  > Can you try the attached tarball. A colleague found and fixed a couple
>  > of issues in my sample including the face that it was including in the
>  > wrong Rules.mk.
>  >
>  > Thanks
>  > Ross
>  >
>  > >
> ------------------------------------------------------------------------
>  > > *From:* Ross Philipson <Ross.Philipson@citrix.com
> <mailto:Ross.Philipson@citrix.com>
>  > <mailto:Ross.Philipson@citrix.com <mailto:Ross.Philipson@citrix.com>>>
>  > > *To:* "xen-devel@lists.xensource.com
> <mailto:xen-devel@lists.xensource.com>
>  > <mailto:xen-devel@lists.xensource.com
> <mailto:xen-devel@lists.xensource.com>>" <xen-devel@lists.xensource.com
> <mailto:xen-devel@lists.xensource.com>
>  > <mailto:xen-devel@lists.xensource.com
> <mailto:xen-devel@lists.xensource.com>>>
>  > > *Cc:* "Art Napor (artnapor@yahoo.com <mailto:artnapor@yahoo.com>
> <mailto:artnapor@yahoo.com <mailto:artnapor@yahoo.com>>)"
>  > <artnapor@yahoo.com <mailto:artnapor@yahoo.com>
> <mailto:artnapor@yahoo.com <mailto:artnapor@yahoo.com>>>
>  > > *Sent:* Tuesday, January 8, 2013 5:04 PM
>  > > *Subject:* HVM firmware passthrough - helper library
>  > >
>  > > Attached is a tarball with a helper library for reading host ACPI and
>  > > SMBIOS firmware and creating firmware files that can be used with the
>  > > HVM firmware passthrough patches I submitted. I used it in my
> testing of
>  > > the patches and planned to use it later when we moved to a new Xen
>  > > version. This library was requested by a few people - I hope you
> find it
>  > > useful.
>  > >
>  > > Ross Philipson
>  > > Senior Software Engineer
>  > > Citrix Systems, Inc
>  > > 14 Crosby Drive
>  > > Bedford, MA 01730
>  > > 781-301-7949
>  > > ross.philipson@citrix.com <mailto:ross.philipson@citrix.com>
> <mailto:ross.philipson@citrix.com <mailto:ross.philipson@citrix.com>>
>  > <mailto:ross.philipson@citrix.com <mailto:ross.philipson@citrix.com>
> <mailto:ross.philipson@citrix.com <mailto:ross.philipson@citrix.com>>>
>  > >
>  >
>  >
>  >
>  >
>  >
>
>
>

  reply	other threads:[~2013-04-01 22:04 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-08 22:04 HVM firmware passthrough - helper library Ross Philipson
2013-01-09 10:44 ` Ian Campbell
2013-01-09 17:57   ` Ross Philipson
2013-02-01 20:26   ` Ross Philipson
2013-02-04 10:24     ` Ian Campbell
2013-02-04 18:42       ` Ross Philipson
     [not found] ` <1363806237.80975.YahooMailNeo@web161405.mail.bf1.yahoo.com>
2013-03-20 20:08   ` Ross Philipson
2013-03-21 19:42     ` Art Napor
2013-03-24 21:10       ` Ross Philipson
2013-03-27  4:50         ` Art Napor
2013-04-01 22:04           ` Ross Philipson [this message]
2013-04-02  3:19             ` Art Napor
2013-04-02 21:15               ` Ross Philipson
2013-04-23 22:06                 ` Art Napor
2013-04-24 13:09                   ` Ross Philipson
2013-09-12 19:29                 ` Art Napor
2013-09-13 13:25                   ` Ross Philipson
2013-09-14 13:45                     ` Andrew Bobulsky

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=515A0480.5000407@citrix.com \
    --to=ross.philipson@citrix.com \
    --cc=artnapor@yahoo.com \
    --cc=xen-devel@lists.xensource.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 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.