From: Gerd Knorr <kraxel@bytesex.org>
To: Robbie Dinn <robbie@microbus.com>
Cc: xen-devel@lists.xensource.com, xen-users@lists.xensource.com,
agruen@suse.de
Subject: Re: xen on suse 9.3 and software raid
Date: Thu, 12 May 2005 16:28:18 +0200 [thread overview]
Message-ID: <20050512142818.GA32316@bytesex> (raw)
In-Reply-To: <20050512135235.GC31317@bytesex>
[ adding xen-devel to Cc: ]
> Just loading the raid6 module in a xen domain makes my
> machine oops, log below. I'd guess it's because the
> module attempts to use mmx within the kernel, which is
> a bit tricky because you have to save/restore userspace
> fp state for that. Could be a corner case which simply
> doesn't work with xen.
Confirmed, the faulting instruction is a attempt to access
cr0, right here:
static inline unsigned long raid6_get_fpu(void)
{
unsigned long cr0;
preempt_disable();
asm volatile("mov %%cr0,%0 ; clts" : "=r" (cr0));
return cr0;
}
(which is called by raid6_before_mmx, which in turn is called by
raid6_mmx1_gen_syndrome, both calls not visible in the trace
because they are inlined).
Ideas how to fix that? Other than just disabling raid6? Can
that code be replaced with xen hypercalls? fsave & frestore
are also used btw. It's all in drivers/md/raid6x86.h
Gerd
--
-mm seems unusually stable at present.
-- akpm about 2.6.12-rc3-mm3
next parent reply other threads:[~2005-05-12 14:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.58.0504262344130.23086@nas.ospex.com>
[not found] ` <4271F381.4010303@microbus.com>
[not found] ` <42720A1B.3010905@microbus.com>
[not found] ` <8764xri5h0.fsf@bytesex.org>
[not found] ` <428218F7.1070605@microbus.com>
[not found] ` <20050512135235.GC31317@bytesex>
2005-05-12 14:28 ` Gerd Knorr [this message]
2005-05-12 15:25 ` Re: [Xen-users] xen on suse 9.3 and software raid Keir Fraser
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=20050512142818.GA32316@bytesex \
--to=kraxel@bytesex.org \
--cc=agruen@suse.de \
--cc=robbie@microbus.com \
--cc=xen-devel@lists.xensource.com \
--cc=xen-users@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.