public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Alex Williamson <alex.williamson@hp.com>
To: Andi Kleen <ak@suse.de>
Cc: Pavel Machek <pavel@ucw.cz>,
	acpi-devel <acpi-devel@lists.sourceforge.net>,
	linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [ACPI] Re: [PATCH/RFC] exposing ACPI objects in sysfs
Date: Tue, 21 Sep 2004 13:13:55 -0600	[thread overview]
Message-ID: <1095794035.24751.54.camel@tdi> (raw)
In-Reply-To: <20040921190606.GE18938@wotan.suse.de>

On Tue, 2004-09-21 at 21:06 +0200, Andi Kleen wrote:
> On Tue, Sep 21, 2004 at 07:26:25PM +0200, Pavel Machek wrote:
> > > +struct special_cmd {
> > > +        u32                     magic;
> > > +        unsigned int            cmd;
> > > +        char                    *args;
> > > +};
> > 
> > Talk to Andi Kleen; passing such structures using read/write is evil,
> > because (unlike ioctl) there's no place to put 32/64bit
> > translation. Imagine i386 application running on x86-64 system.
> 
> Yes, Pavel is right. Please don't pass pointers by read/write
> because it cannot be 32bit emulated.

   All pointers are actually interpreted as offsets into the buffer for
this interface.  They are not actually pointers.  I believe the 32bit
emulation problem is limited to an ILP32 application generating data
structures appropriate for an LP64 kernel.  While difficult, it can be
done.

	Alex

-- 
Alex Williamson                             HP Linux & Open Source Lab

  reply	other threads:[~2004-09-21 19:13 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-20 21:41 [PATCH/RFC] exposing ACPI objects in sysfs Alex Williamson
2004-09-21 12:24 ` Pavel Machek
2004-09-21 14:18   ` Alex Williamson
2004-09-21 16:48   ` Alex Williamson
2004-09-21 17:26     ` Pavel Machek
2004-09-21 18:00       ` Alex Williamson
2004-09-21 19:31         ` Pavel Machek
2004-09-21 19:06       ` [ACPI] " Andi Kleen
2004-09-21 19:13         ` Alex Williamson [this message]
2004-09-21 19:18           ` Andi Kleen
2004-09-21 19:45             ` Alex Williamson
2004-09-21 19:58               ` Pavel Machek
2004-09-21 20:40                 ` Alex Williamson
2004-09-21 21:02                   ` Pavel Machek
     [not found]                     ` <20040921210218.GJ30425-I/5MKhXcvmPrBKCeMvbIDA@public.gmane.org>
2004-10-15 22:39                       ` Alex Williamson
2004-10-26 20:55                         ` [RFC] dev_acpi: support for userspace access to acpi Alex Williamson
2004-09-21 19:21           ` [ACPI] Re: [PATCH/RFC] exposing ACPI objects in sysfs Arjan van de Ven

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=1095794035.24751.54.camel@tdi \
    --to=alex.williamson@hp.com \
    --cc=acpi-devel@lists.sourceforge.net \
    --cc=ak@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pavel@ucw.cz \
    /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