hi,
a. Ok I will re-enable the cmpxchg8b. b. I am not sure about the changes and since it occurs quite rarely, I am not sure if it is a case of not cleaning up interrupts properly after a crash.
I will live with them for now and get back to this once the other issues are sorted out.
thanks, Ramya ________________________________________ From: l4-hackers [l4-hackers-bounces@os.inf.tu-dresden.de] on behalf of Adam Lackorzynski [adam@os.inf.tu-dresden.de] Sent: 09 September 2014 22:46 To: l4-hackers@os.inf.tu-dresden.de Subject: Re: Aborted L4linux due to CLI/STI
Hi,
On Mon Sep 08, 2014 at 07:10:00 +0000, Masti Ramya Jayaram wrote:
That's ok as long it's also ok for native Linux.
I am not sure what they did with native Linux but I know from the SCC forums that these instructions do not exist. So I guess that is ok.
I'm wondering how did you end up with the code containing the cli? In L4Linux this part is replaced.
Well, I am not sure about that. I did force a couple of options though as I already mentioned. The reason was that when I tried to compile L4linux for pentium/i586, I saw that it would complain about CONFIG_X86_CMPXCHG64 not being enabled (this corresponds to the PAE option). So I disabled this explicitly since the processors on the SCC do not contain PAE. I also disabled the CONFIG_X86_CMPXCHG and CONFIG_CMPXCHG_LOCAL options.
As far as I know the SCC does have a cmpxchg8b so you could just make Linux use that by tweaking the config.
Attached is my l4linux config. Just as a note, I am using quite an old build of L4linux. Do you know of any related bugs?
Uh, that's old. There are probably many. Were there any significant changes to that version?
Adam -- Adam adam@os.inf.tu-dresden.de Lackorzynski http://os.inf.tu-dresden.de/~adam/
_______________________________________________ l4-hackers mailing list l4-hackers@os.inf.tu-dresden.de http://os.inf.tu-dresden.de/mailman/listinfo/l4-hackers