This patch moves lguest's loader Makefile one level bellow, and adds
arch-specific code to arch directories
Signed-off-by: Glauber de Oliveira Costa <[EMAIL PROTECTED]>
--
Glauber de Oliveira Costa
Red Hat Inc.
"Free as in Freedom"
--- i386/Makefile 2007-04-02 16:
All that is left for the architectures, is the room for some specific
definitions.
Signed-off-by: Glauber de Oliveira Costa <[EMAIL PROTECTED]>
--
Glauber de Oliveira Costa
Red Hat Inc.
"Free as in Freedom"
--- /dev/null 2007-04-02 15:35:49.510433377 -0300
+++ i386/lguest_de
d-off-by: Glauber de Oliveira Costa <[EMAIL PROTECTED]>
--
Glauber de Oliveira Costa
Red Hat Inc.
"Free as in Freedom"
--- i386/lguest.c 2007-04-02 16:19:27.0 -0300
+++ lguest.c2007-04-02 16:19:28.0 -0300
@@ -29,11 +29,22 @@
#include
#include
#include
Setting the DEBUG_SIG flag breaks compilation due to a wrong
struct access. Aditionally, it raises two warnings. This is one
patch to fix them all.
Signed-off-by: Glauber de Oliveira Costa <[EMAIL PROTECTED]>
--
Glauber de Oliveira Costa
Red Hat Inc.
"Free as in Free
There is (was) yet another function to load something into
the cr3 register. We don't need it.
Signed-off-by: Glauber de Oliveira Costa <[EMAIL PROTECTED]>
--
Glauber de Oliveira Costa
Red Hat Inc.
"Free as in Freedom"
diff --git a/arch/x86_64/kernel/smp.c b/arch/x86_
- note PT_NOTE FLAGS(4); /* R__ */
+ note PT_NOTE FLAGS(0); /* ___ */
}
This seems to happen in at least 3 more architectures. Worth a broader cleanup?
--
Glauber de Oliveira Costa.
"Free as in Freedom"
"The less confident you are, the more serious you hav
On Tue, Mar 13, 2007 at 05:33:09AM -0700, Randy.Dunlap wrote:
> On Tue, 13 Mar 2007, Glauber de Oliveira Costa wrote:
>
> > Tiny cleanup:
> >
> > In x86_64, the same functions for reading cr3 and writing cr{3,4} are
> > defined in tlbflush.h and system.h, whith ju
.
write_cr3() is moved to system.h for consistency.
Signed-off-by: Glauber de Oliveira Costa <[EMAIL PROTECTED]>
--
Glauber de Oliveira Costa
Red Hat Inc.
"Free as in Freedom"
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message
On Sat, Feb 24, 2007 at 02:12:29PM -0500, Chuck Ebbert wrote:
>
> Umm, it's already there, right after the word "Oops".
>
>
> Oops: 0002 [1] SMP
> ^^^^
Oops! ;-)
--
Glauber de Oliveira Costa
Red Hat Inc.
"Free as in Freedom"
-
To unsubscribe
When a page faults comes from a kernel space, the printed summary
leaves us clueless about what kind of access was being tried (which
is encoded in the error_code variable).
Having it promply available may ease debugging in a bunch of
situations.
Signed-off-by: Glauber de Oliveira Costa <[EM
Pointers to user data should be marked with a __user hint. This one is missing.
Signed-off-by: Glauber de Oliveira Costa <[EMAIL PROTECTED]>
---
fs/proc/base.c |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/fs/proc/base.c b/fs/proc/base.c
index 4f5745a..01f7769
This is a tiny cleanup to increase readability
Signed-off-by: Glauber de Oliveira Costa <[EMAIL PROTECTED]>
--
Glauber de Oliveira Costa
Red Hat Inc.
"Free as in Freedom"
diff -Nrup linux-2.6.19.1/arch/x86_64/kernel/ioport.c
linux-2.6.19.1-devel/arch/x86_64/kernel/ioport.c
--
Oops ;-) resending, as I forgot to sign last version:
Unlike x86, x86_64 already passes arguments in registers. The use of
regparm attribute makes no difference in produced code, and the use of
fastcall just bloats the code.
Signed-off-by: Glauber de Oliveira Costa <[EMAIL PROTEC
Unlike x86, x86_64 already passes arguments in registers. The use of
regparm attribute makes no difference in produced code, and the use of
fastcall just bloats the code.
--
Glauber de Oliveira Costa
Red Hat Inc.
"Free as in Freedom"
diff -rup linux-2.6.19.1-devel/arch/x86_64/k
ext3_setup_new_group_blocks was simply wiped out, since this
is always called from one of the functions that already holds the lock
(and thus, in a safe environment)
Signed-off-by: Glauber de Oliveira Costa <[EMAIL PROTECTED]>
--
=
Glauber de Oliveira Costa
IBM Linux Technology
we become pretty much independent of vfs
locking decisions to handle ext3 data. Do you think it all make sense?
--
=========
Glauber de Oliveira Costa
IBM Linux Technology Center - Brazil
[EMAIL PROTECTED]
=
-
To unsubscribe from thi
> NAK, this is wrong:
>
> > + lock_super(sb);
> > err = ext3_group_extend(sb, EXT3_SB(sb)->s_es, n_blocks_count);
> > + unlock_super(sb);
>
> This basically reverses the order of locking between lock_super() and
> journal_start() (the latter acts like a lock beca
This simple patch provides a fix for a locking issue found in the online
resizing code. The problem actually happened while trying to resize the
filesystem trough the resize=xxx option in a remount.
Signed-off-by: Glauber de Oliveira Costa <[EMAIL PROTECTED]>
diff -up linux-2.6.13-rc6-o
501 - 518 of 518 matches
Mail list logo