linux-um archives
 help / color / mirror / Atom feed
From: Antoine Martin <antoine@nagafix.co.uk>
To: Daniel Gryniewicz <dang@gentoo.org>
Cc: Jeff Dike <jdike@addtoit.com>,
	user-mode-linux-devel@lists.sourceforge.net
Subject: Re: [uml-devel] ARCH=um SUBARCH=i386 breakage?
Date: Thu, 19 Jul 2007 20:54:14 +0100	[thread overview]
Message-ID: <469FC166.6050209@nagafix.co.uk> (raw)
In-Reply-To: <1184807588.7782.1.camel@athena.fprintf.net>

Daniel Gryniewicz wrote:
> On Sun, 2007-07-15 at 18:08 +0100, Antoine Martin wrote:
>   
>> Jeff Dike wrote:
>>     
>>> On Sat, Jul 14, 2007 at 10:23:25AM +0100, Antoine Martin wrote:
>>>   
>>>       
>>>> I don't mind bugging people to get to the bottom of this, do you know 
>>>> where to knock?
>>>> I can't find anything in MAINTAINERS.
>>>>     
>>>>         
>>> Did you install the headers directly from a kernel tree, or is this
>>> the result of a distro upgrade?
>>>   
>>>       
>> These are the Gentoo packages which are very close to mainline and I 
>> can't find the upstream location for the headers so I guess I will be 
>> filing a bug with Gentoo... We'll see where that leads.
>>
>>     
>
> Actually, the Gentoo headers are not particularly close to the kernel
> headers. 
My mistake.
>  They are heavily "sanitized", meaning that all kinds of things
> that userspace is "not supposed to use" are removed. 
So in a sense, Gentoo kernel headers are ahead of the game. Which means 
that these changes are likely to become an issue not just for Gentoo 
users in the future.

>  This makes it very
> hard for things like UML, that are heavily tied to the kernel, to build.
>   
As Jeff pointed out, this is part of the userspace api:
"the elimination of user.h makes it impossible to use 
PTRACE_SETFP[X]REGS, as there is no way to tell what size buffer should 
be passed in."

Can you suggest a way to code around this issue or is this going to require an update to the Gentoo kernel headers?
Let me know if I can help.

Thanks
Antoine


-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel

      parent reply	other threads:[~2007-07-19 19:54 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-13 11:06 [uml-devel] ARCH=um SUBARCH=i386 breakage? Antoine Martin
2007-07-13 12:03 ` Antoine Martin
2007-07-13 15:57   ` Jeff Dike
2007-07-13 17:41     ` Antoine Martin
2007-07-13 18:44       ` Jeff Dike
2007-07-14  9:23         ` Antoine Martin
2007-07-14 12:00           ` Jeff Dike
2007-07-15 17:08             ` Antoine Martin
2007-07-19  1:13               ` Daniel Gryniewicz
2007-07-19  1:25                 ` Jeff Dike
2007-07-19 19:54                 ` Antoine Martin [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=469FC166.6050209@nagafix.co.uk \
    --to=antoine@nagafix.co.uk \
    --cc=dang@gentoo.org \
    --cc=jdike@addtoit.com \
    --cc=user-mode-linux-devel@lists.sourceforge.net \
    /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