All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeremy Fitzhardinge <jeremy@goop.org>
To: "Sven Köhler" <sven.koehler@gmail.com>
Cc: xen-devel@lists.xensource.com, xen-users@lists.xensource.com
Subject: Re: Re: 2.6.28.7 domU: 32-bit emulation seems to be broken
Date: Mon, 16 Mar 2009 13:20:23 -0700	[thread overview]
Message-ID: <49BEB487.3090503@goop.org> (raw)
In-Reply-To: <49BD3A87.3060403@gmail.com>

Sven Köhler wrote:
> Jeremy Fitzhardinge schrieb:
>   
>> Sven Köhler wrote:
>>     
>>> Jeremy Fitzhardinge schrieb:
>>>  
>>>       
>>>> Has it ever worked?  If so, what kernel version did it stop working
>>>> at?     
>>>>         
>>> I've just tried a good old non-pv_ops 2.6.18 kernel:
>>>
>>> I ran the same binary file, that segfaults on 2.6.28.7.
>>> It runs just fine on 2.6.18.
>>>
>>> I haven't tested any other pc_ops kernel version. I'm not sure, that it
>>> ever worked with these kernel. Which was the first kernel version, that
>>> had domU support? 2.6.28.0 ?
>>>
>>>   
>>>       
>> Does this patch help?
>>
>> diff --git a/arch/x86/ia32/ia32entry.S b/arch/x86/ia32/ia32entry.S
>> index e4baa06..3ea8299 100644
>> --- a/arch/x86/ia32/ia32entry.S
>> +++ b/arch/x86/ia32/ia32entry.S
>> @@ -400,7 +400,6 @@ ENTRY(ia32_syscall)
>>     /*CFI_REL_OFFSET    rflags,EFLAGS-RIP*/
>>     /*CFI_REL_OFFSET    cs,CS-RIP*/
>>     CFI_REL_OFFSET    rip,RIP-RIP
>> -    PARAVIRT_ADJUST_EXCEPTION_FRAME
>>     SWAPGS
>>     /*
>>      * No need to follow this irqs on/off section: the syscall
>>     
>
> No, still segfaults :-(
>   

Do you have auditing enabled?

    J

  reply	other threads:[~2009-03-16 20:20 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <gpe0vg$j67$1@ger.gmane.org>
2009-03-13 21:11 ` 2.6.28.7 domU: 32-bit emulation seems to be broken Sven Köhler
2009-03-14  0:38   ` Jeremy Fitzhardinge
2009-03-14  0:59     ` Jeremy Fitzhardinge
2009-03-14  8:48       ` Sven Köhler
2009-03-14 22:03         ` Jeremy Fitzhardinge
2009-03-15 11:39           ` Sven Köhler
2009-03-15 15:32             ` Jeremy Fitzhardinge
2009-03-15 17:43               ` Sven Köhler
2009-03-15 17:45                 ` Jeremy Fitzhardinge
2009-03-15 22:18                   ` [Xen-devel] " Sven Köhler
2009-03-15 22:21                     ` Sven Köhler
2009-03-15 17:48                 ` Jeremy Fitzhardinge
2009-03-15 12:24           ` Sven Köhler
2009-03-15 13:30             ` [Xen-users] " Boris Derzhavets
2009-03-15 15:32             ` Jeremy Fitzhardinge
2009-03-15 16:28             ` Jeremy Fitzhardinge
2009-03-15 17:27               ` [Xen-devel] " Sven Köhler
2009-03-16 20:20                 ` Jeremy Fitzhardinge [this message]
2009-03-16 20:23                   ` Jeremy Fitzhardinge
2009-03-16 22:29                     ` Sven Köhler
2009-03-16 22:36                       ` Jeremy Fitzhardinge
2009-03-17 14:08                         ` Sven Köhler
2009-03-17 16:52                           ` Jeremy Fitzhardinge
2009-03-17 20:31                             ` [Xen-devel] " Sven Köhler
2009-03-17 21:14                               ` Jeremy Fitzhardinge
2009-08-10 11:21                             ` Milan Holzäpfel
2009-08-10 12:59                               ` Christoph Egger
2009-08-11  7:36                                 ` Milan Holzäpfel
2009-08-14 20:55                                 ` Jeremy Fitzhardinge
2009-03-14  9:13     ` [Xen-devel] " Sven Köhler

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=49BEB487.3090503@goop.org \
    --to=jeremy@goop.org \
    --cc=sven.koehler@gmail.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.