From: Daniel Gryniewicz <dang@gentoo.org>
To: Paolo Giarrusso <blaisorblade@yahoo.it>
Cc: Andi Kleen <ak@suse.de>, Jeff Dike <jdike@addtoit.com>,
linux-kernel@vger.kernel.org,
user-mode-linux-devel@lists.sourceforge.net
Subject: Re: [uml-devel] [PATCH 1/3] uml: use -mcmodel=kernel for x86_64
Date: Tue, 08 Aug 2006 10:47:55 -0400 [thread overview]
Message-ID: <1155048476.18932.17.camel@athena.fprintf.net> (raw)
In-Reply-To: <20060808140335.81959.qmail@web25219.mail.ukl.yahoo.com>
[-- Attachment #1: Type: text/plain, Size: 331 bytes --]
On Tue, 2006-08-08 at 16:03 +0200, Paolo Giarrusso wrote:
> Moreover, who has recently tested module loading in x86-64 uml
> kernels? I don't remember doing such testing recently...
>
Well, modules seem to work fine here on x86_64. I'm running 2.6.16-bs2.
I only tested the loop module, but others also load.
Daniel
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
prev parent reply other threads:[~2006-08-08 14:48 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-06 15:47 [PATCH 1/3] uml: use -mcmodel=kernel for x86_64 Paolo 'Blaisorblade' Giarrusso
2006-08-06 15:47 ` [PATCH 2/3] uml: fix proc-vs-interrupt context spinlock deadlock Paolo 'Blaisorblade' Giarrusso
2006-08-07 22:14 ` Jeff Dike
2006-08-08 10:59 ` Paolo Giarrusso
2006-08-08 20:02 ` Jeff Dike
2006-08-09 14:44 ` Paolo Giarrusso
2006-08-06 15:47 ` [PATCH 3/3] uml: clean our set_ether_mac Paolo 'Blaisorblade' Giarrusso
2006-08-07 22:17 ` Jeff Dike
2006-08-07 21:18 ` [PATCH 1/3] uml: use -mcmodel=kernel for x86_64 Jeff Dike
2006-08-08 10:46 ` Paolo Giarrusso
2006-08-08 11:22 ` Andi Kleen
2006-08-08 14:03 ` Paolo Giarrusso
2006-08-08 14:14 ` Andi Kleen
2006-08-08 14:47 ` Daniel Gryniewicz [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=1155048476.18932.17.camel@athena.fprintf.net \
--to=dang@gentoo.org \
--cc=ak@suse.de \
--cc=blaisorblade@yahoo.it \
--cc=jdike@addtoit.com \
--cc=linux-kernel@vger.kernel.org \
--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