That ioctl does not transfer any data, so it should be an _IO rather than an
_IOW.
Signed-off-by: Avi Kivity <[EMAIL PROTECTED]>
---
include/linux/kvm.h |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/include/linux/kvm.h b/include/linux/kvm.h
index c6dd4a7..d89189a
This is redundant, as we also return -EINTR from the ioctl, but it
allows us to examine the exit_reason field on resume without seeing
old data.
Signed-off-by: Avi Kivity <[EMAIL PROTECTED]>
---
drivers/kvm/svm.c |2 ++
drivers/kvm/vmx.c |2 ++
include/linux/kvm.h |3 ++-
3 files
This allows users to actually build prgrams that use kvm without
the entire source tree.
Signed-off-by: Avi Kivity <[EMAIL PROTECTED]>
---
include/linux/Kbuild |1 +
1 files changed, 1 insertions(+), 0 deletions(-)
diff --git a/include/linux/Kbuild b/include/linux/Kbuild
index
Signed-off-by: Avi Kivity <[EMAIL PROTECTED]>
---
drivers/kvm/kvm_main.c |6 ++
include/linux/kvm.h|5 +
2 files changed, 11 insertions(+), 0 deletions(-)
diff --git a/drivers/kvm/kvm_main.c b/drivers/kvm/kvm_main.c
index 5d24203..39cf8fd 100644
--- a/drivers/kvm/kvm_main.c
We no longer emulate single instructions in userspace. Instead, we service
mmio or pio requests.
Signed-off-by: Avi Kivity <[EMAIL PROTECTED]>
---
drivers/kvm/kvm_main.c |5 -
include/linux/kvm.h|3 +--
2 files changed, 1 insertions(+), 7 deletions(-)
diff --git
This allows us to store offsets in the kernel/user kvm_run area, and be
sure that userspace has them mapped. As offsets can be outside the
kvm_run struct, userspace has no way of knowing how much to mmap.
Signed-off-by: Avi Kivity <[EMAIL PROTECTED]>
---
drivers/kvm/kvm_main.c |8 +++-
This is useful for paravirtualized graphics devices, for example.
Signed-off-by: Avi Kivity <[EMAIL PROTECTED]>
---
drivers/kvm/kvm_main.c | 18 +-
include/linux/kvm.h| 10 +-
2 files changed, 26 insertions(+), 2 deletions(-)
diff --git a/drivers/kvm/kvm_main.c
The recent changes have left the ioctl numbers in complete disarray.
Signed-off-by: Avi Kivity <[EMAIL PROTECTED]>
---
include/linux/kvm.h | 34 +-
1 files changed, 17 insertions(+), 17 deletions(-)
diff --git a/include/linux/kvm.h b/include/linux/kvm.h
index
Currently, userspace is told about the nature of the last exit from the
guest using two fields, exit_type and exit_reason, where exit_type has
just two enumerations (and no need for more). So fold exit_type into
exit_reason, reducing the complexity of determining what really happened.
Allow a special signal mask to be used while executing in guest mode. This
allows signals to be used to interrupt a vcpu without requiring signal
delivery to a userspace handler, which is quite expensive. Userspace still
receives -EINTR and can get the signal via sigwait().
Signed-off-by: Avi
Older userspace didn't care, but newer userspace (with the cpuid changes)
does.
Signed-off-by: Avi Kivity <[EMAIL PROTECTED]>
---
drivers/kvm/svm.c |3 +++
1 files changed, 3 insertions(+), 0 deletions(-)
diff --git a/drivers/kvm/svm.c b/drivers/kvm/svm.c
index 0311665..2396ada 100644
---
On Sunday 01 April 2007, Ingo Molnar wrote:
>* Gene Heskett <[EMAIL PROTECTED]> wrote:
>> Hi Ingo;
>>
>> Running 2.6.21-rc5 tonight.
>>
>> It appears that as of 2.6.21-rc5, (actually anything with a 2.6.21 in
>> its version string) amanda is still a loser. [...]
>
>here 'is a loser' means: "tries
set_cr0_no_modeswitch() was a hack to avoid corrupting segment registers.
As we now cache the protected mode values on entry to real mode, this
isn't an issue anymore, and it interferes with reboot (which usually _is_
a modeswitch).
Signed-off-by: Avi Kivity <[EMAIL PROTECTED]>
---
Some ioctls ignore their arguments. By requiring them to be zero now,
we allow a nonzero value to have some special meaning in the future.
Signed-off-by: Avi Kivity <[EMAIL PROTECTED]>
---
drivers/kvm/kvm_main.c |9 +
1 files changed, 9 insertions(+), 0 deletions(-)
diff --git
The cpu cache is a host resource; the guest should not be able to turn
it off (even for itself).
Signed-off-by: Avi Kivity <[EMAIL PROTECTED]>
---
drivers/kvm/svm.c |4 +++-
1 files changed, 3 insertions(+), 1 deletions(-)
diff --git a/drivers/kvm/svm.c b/drivers/kvm/svm.c
index
The SET_SREGS ioctl modifies both cr0.pe (real mode/protected mode) and
guest segment registers. Since segment handling is modified by the mode on
Intel procesors, update the segment registers after the mode switch has taken
place.
Signed-off-by: Avi Kivity <[EMAIL PROTECTED]>
---
The reset state has cs.selector == 0xf000 and cs.base == 0x,
which aren't compatible with vm86 mode, which is used for real mode
virtualization.
When we create a vcpu, we set cs.base to 0xf, but if we get there by
way of a reset, the values are inconsistent and vmx refuses to enter
From: Sergey Kiselev <[EMAIL PROTECTED]>
Some older (~2.6.7) kernels write MCG_STATUS register during kernel
boot (mce_clear_all() function, called from mce_init()). It's not
currently handled by kvm and will cause it to inject a GPF.
Following patch adds a "nop" handler for this.
Signed-off-by:
From: Michal Piotrowski <[EMAIL PROTECTED]>
Remove unused function
CC drivers/kvm/svm.o
drivers/kvm/svm.c:207: warning: ‘inject_db’ defined but not used
Signed-off-by: Michal Piotrowski <[EMAIL PROTECTED]>
Signed-off-by: Avi Kivity <[EMAIL PROTECTED]>
---
drivers/kvm/svm.c |7 ---
From: Dor Laor <[EMAIL PROTECTED]>
Instead of twiddling the rip registers directly, use the
skip_emulated_instruction() function to do that for us.
Signed-off-by: Dor Laor <[EMAIL PROTECTED]>
Signed-off-by: Avi Kivity <[EMAIL PROTECTED]>
---
drivers/kvm/svm.c |3 ++-
drivers/kvm/vmx.c |
We already special case the pdptr access, so no need to check it again.
Signed-off-by: Avi Kivity <[EMAIL PROTECTED]>
---
drivers/kvm/paging_tmpl.h |3 +--
1 files changed, 1 insertions(+), 2 deletions(-)
diff --git a/drivers/kvm/paging_tmpl.h b/drivers/kvm/paging_tmpl.h
index
The current string pio interface communicates using guest virtual addresses,
relying on userspace to translate addresses and to check permissions. This
interface cannot fully support guest smp, as the check needs to take into
account two pages at one in case an unaligned string transfer straddles
No longer interesting.
Signed-off-by: Avi Kivity <[EMAIL PROTECTED]>
---
drivers/kvm/vmx.c |1 -
1 files changed, 0 insertions(+), 1 deletions(-)
diff --git a/drivers/kvm/vmx.c b/drivers/kvm/vmx.c
index 578dff5..b64b7b7 100644
--- a/drivers/kvm/vmx.c
+++ b/drivers/kvm/vmx.c
@@ -1131,7
The initial, noncaching, version of the kvm mmu flushed the all nonglobal
shadow page table translations (much like a native tlb flush). The new
implementation flushes translations only when they change, rendering global
pte tracking superfluous.
This removes the unused tracking mechanism and
Following is my current 2.6.22 kvm queue. It contains userspace interface
updates, improved guest support, cleanups, and plain bugfixes. It will
likely grow slightly by the time the merge window opens.
Avi Kivity (34):
KVM: Use own minor number
KVM: Export
KVM: Fix bogus sign
As usual, we need to mangle segment registers when emulating real mode
as vm86 has specific constraints. We special case the reset segment base,
and set the "access rights" (or descriptor flags) to vm86 comaptible values.
This fixes reboot on vmx.
Signed-off-by: Avi Kivity <[EMAIL PROTECTED]>
The kvm mmu keeps a shadow page for hugepage pdes; if several such pdes map
the same physical address, they share the same shadow page. This is a fairly
common case (kernel mappings on i386 nonpae Linux, for example).
However, if the two pdes map the same memory but with different permissions,
From: Joerg Roedel <[EMAIL PROTECTED]>
This patch forbids the guest to execute monitor/mwait instructions on
SVM. This is necessary because the guest can execute these instructions
if they are available even if the kvm cpuid doesn't report its
existence.
Signed-off-by: Joerg Roedel <[EMAIL
From: Dor Laor <[EMAIL PROTECTED]>
Functions that play around with the physical memory map
need a way to clear mappings to possibly nonexistent or
invalid memory. Both the mmu cache and the processor tlb
are cleared.
Signed-off-by: Dor Laor <[EMAIL PROTECTED]>
Signed-off-by: Avi Kivity <[EMAIL
Trivial cleanup.
Signed-off-by: Avi Kivity <[EMAIL PROTECTED]>
---
drivers/kvm/kvm_svm.h |2 --
drivers/kvm/svm.c |2 --
2 files changed, 0 insertions(+), 4 deletions(-)
diff --git a/drivers/kvm/kvm_svm.h b/drivers/kvm/kvm_svm.h
index 624f1ca..a1a9eba 100644
---
These are really helpful when migrating an floating point app to another
machine.
Signed-off-by: Avi Kivity <[EMAIL PROTECTED]>
---
drivers/kvm/kvm_main.c | 86
include/linux/kvm.h| 17 +
2 files changed, 103 insertions(+), 0
When auditing a 32-bit guest on a 64-bit host, sign extension of the page
table directory pointer table index caused bogus addresses to be shown on
audit errors.
Fix by declaring the index unsigned.
Signed-off-by: Avi Kivity <[EMAIL PROTECTED]>
---
drivers/kvm/mmu.c |2 +-
1 files changed,
On x86, bit operations operate on a string of bits that can reside in
multiple words. For example, 'btsl %eax, (blah)' will touch the word
at blah+4 if %eax is between 32 and 63.
The x86 emulator compensates for that by advancing the operand address
by (bit offset / BITS_PER_LONG) and truncating
With this, we can specify that accesses to one physical memory range will
be remapped to another. This is useful for the vga window at 0xa which
is used as a movable window into the (much larger) framebuffer.
Signed-off-by: Avi Kivity <[EMAIL PROTECTED]>
---
drivers/kvm/kvm.h |9
Use list_move() where possible. Noticed by Dor Laor.
Signed-off-by: Avi Kivity <[EMAIL PROTECTED]>
---
drivers/kvm/mmu.c | 12
1 files changed, 4 insertions(+), 8 deletions(-)
diff --git a/drivers/kvm/mmu.c b/drivers/kvm/mmu.c
index 0216b77..c2487b6 100644
---
Mapping a guest page to a host page is a common operation. Currently,
one has first to find the memory slot where the page belongs (gfn_to_memslot),
then locate the page itself (gfn_to_page()).
This is clumsy, and also won't work well with memory aliases. So simplify
gfn_to_page() not to
When a vcpu is migrated from one cpu to another, its timestamp counter
may lose its monotonic property if the host has unsynced timestamp counters.
This can confuse the guest, sometimes to the point of refusing to boot.
As the rdtsc instruction is rather fast on AMD processors (7-10 cycles),
we
Instead of passing a 'struct kvm_run' back and forth between the kernel and
userspace, allocate a page and allow the user to mmap() it. This reduces
needless copying and makes the interface expandable by providing lots of
free space.
Signed-off-by: Avi Kivity <[EMAIL PROTECTED]>
---
From: Joerg Roedel <[EMAIL PROTECTED]>
This patch enables the virtualization of the last branch record MSRs on
SVM if this feature is available in hardware. It also introduces a small
and simple check feature for specific SVM extensions.
Signed-off-by: Joerg Roedel <[EMAIL PROTECTED]>
From: Dor Laor <[EMAIL PROTECTED]>
The hypercall code mixes up the ->cache_regs() and ->decache_regs()
callbacks, resulting in guest register corruption.
Signed-off-by: Dor Laor <[EMAIL PROTECTED]>
Signed-off-by: Avi Kivity <[EMAIL PROTECTED]>
---
drivers/kvm/kvm_main.c |4 ++--
1 files
Use the minor number (232) allocated to kvm by lanana.
Signed-off-by: Avi Kivity <[EMAIL PROTECTED]>
---
drivers/kvm/kvm_main.c |2 +-
include/linux/miscdevice.h |1 +
2 files changed, 2 insertions(+), 1 deletions(-)
mode change 100644 => 100755 drivers/kvm/kvm_main.c
diff --git
(resent due to a combination of mailer stupidity and my own
I had to mangle Padraig's name to make it stop encoding as
Quoted-Printable. hope this is palatable. sorry for the resends)
Hello,
Tested and working on Kontron JREX-PM.
fairly straightforward backport of w83627hf_wdt.c from 2.6.20.1
(resent due to mailer stupidity)
Hello,
This is my first submitted kernel patch, please be gentle.
Tested and working on AAEON GENE-6310B Subcompact Board
(also configured for same by default, should work elsewhere)
patch is against kernel 2.4.34.2
Changes/Features:
Added ioctl support
Hello,
Tested and working on Kontron JREX-PM.
fairly straightforward backport of w83627hf_wdt.c from 2.6.20.1
Changes from 2.6 version
Default timeout set to 120 seconds
Nonstandard read only proc interface (/proc/watchdog)
Always reset timer on driver load
Changed timeout limit to 255
Ignores
Hello,
This is my first submitted kernel patch, please be gentle.
Tested and working on AAEON GENE-6310B Subcompact Board
(also configured for same by default, should work elsewhere)
patch is against kernel 2.4.34.2
Changes/Features:
Added ioctl support
Disables watchdog on driver load
Hi,
On 01/04/07, Sascha Curth <[EMAIL PROTECTED]> wrote:
Hi,
i hav essen this in my logfiles. The server wasn't rechable any more and
a hard reset was needed
Yes, that's a bug.
Kernel: 2.6.18
Logfile:
Mar 29 22:18:07 seven [ cut here ]
Mar 29 22:18:07 seven
On 4/1/07, Parag Warudkar <[EMAIL PROTECTED]> wrote:
>- kobject_add(>kobj);
>+ if (kobject_add(>kobj)) {
>+ kfree(p);
>+ return;
Please add a printk warning before the return statement to log a
proper warning stating what happened, which file and line etc.
Aaron Lehmann <[EMAIL PROTECTED]> writes:
[adding netdev]
[meta-comment: I wish people wouldn't use such unnecessarily broad subjects
-- how is it the x86-64 port's or AMD's fault when you have broken hardware?
Would anybody write "Silent corruption on i386" or "Silent corruption
on Intel" or
From: Michal Januszewski <[EMAIL PROTECTED]>
When the cursor and echo are disabled on the current console, pressing a
key will cause a black rectangle to be painted in the cursor's position.
Fix this by not touching the framebuffer in fbcon_cursor() when the
cursor is off.
Signed-off-by: Michal
From: Michal Januszewski <[EMAIL PROTECTED]>
On a multiprocessor machine the VT_WAITACTIVE ioctl call may return 0
if fg_console has already been updated in redraw_screen() but the
console switch itself hasn't been completed. Fix this by checking
fg_console in vt_waitactive() with the console sem
Linux and OpenSource is evolution - go on and create your closed source drivers
and do your own closed-source fork - go on and create your own little homo
neanderthalensis !
___
SMS schreiben mit WEB.DE FreeMail - einfach, schnell und
ROUND_UP(32|64) cleanup, use ALIGN
Signed-off-by: Milind Arun Choudhary <[EMAIL PROTECTED]>
---
sysirix.c |6 ++
1 files changed, 2 insertions(+), 4 deletions(-)
diff --git a/arch/mips/kernel/sysirix.c b/arch/mips/kernel/sysirix.c
index 93a1484..59c25bc 100644
---
On 3/30/07, Pete Zaitcev <[EMAIL PROTECTED]> wrote:
Dell people (Stuart and Charles) complained that on some USB keyboards,
if BIOS enables NumLock, it stays on even after Linux has started. Since
we always start with NumLock off, this confuses users. Quick double dab
at NumLock fixes it, but
Neil Brown wrote:
Definitely the cause. If you really need to add this array, you may
be able to reduce the usage of the array, then reduce the size of the
array, then add the drive.
Depending on how you have partitioned the array, and how you are using
the partitions, you may just need to
ROUND_UP macro cleanup, use ALIGN where ever appropriate
Signed-off-by: Milind Arun Choudhary <[EMAIL PROTECTED]>
---
hotplug/cpci_hotplug_pci.c |2 --
setup-bus.c|8 +++-
2 files changed, 3 insertions(+), 7 deletions(-)
diff --git
not sure if this is a real issue and if it`s UML or loop related - but how is
low-memory situations being handled when creating loop devices ?
should losetup or dmesg tell "out of memory" if there is not enough memory left
?
i fired up my 2.6.20 UML and tried to create lots of loop-devices.
On Sunday 01 April 2007 09:10, Christoph Lameter wrote:
> x86_64 make SPARSE_VIRTUAL the default
>
> x86_64 is using 2M page table entries to map its 1-1 kernel space.
> We implement the virtual memmap also using 2M page table entries.
> So there is no difference at all to FLATMEM. Both schemes
From: Jan Beulich <[EMAIL PROTECTED]>
Commit 2e3646e51b2d6415549b310655df63e7e0d7a080 changed the way
the split config tree is built, but failed to also adjust fixdep
accordingly - if changing a config option from or to m, files
referencing the respective CONFIG_..._MODULE (but not the
On Sat, Mar 31, 2007 at 01:11:29AM -0700, Pedram M wrote:
> Hi,
>
> I've seen this around, and have heard about it in forums and else-where,
> could somebody enlighten me with more information or with experiences
> they have had. Looks like kswapd begins to eat CPU dramatically till the
> box
On 4/1/07, Pekka Enberg <[EMAIL PROTECTED]> wrote:
Looks like mcdx_xfer is sleeping while holding q->queue_lock. The
attached (untested) patch should fix it.
You also need to add a spin_lock_irq() before the call to
end_request() to Jens' patch.
-
To unsubscribe from this list: send the line
On 3/31/07, Rene Herman <[EMAIL PROTECTED]> wrote:
There's quite a bit of noise in dmesg though. Repeated 5 times:
===BUG: scheduling while atomic: mount/0x0001/1166
[] __sched_text_start+0x57/0x574
[] schedule_timeout+0x70/0x8f
[] process_timeout+0x0/0x5
[]
On Sunday April 1, [EMAIL PROTECTED] wrote:
> Neil Brown wrote:
> > On Saturday March 31, [EMAIL PROTECTED] wrote:
> >> hi list!
> >>
> >> in short:
> >> I created a partitioned raid6 array with 2 missing drives. Now, I want to
> >> add a device. It fails with:
> >> flockmock ~ # mdadm -a
On Sat, March 31, 2007 15:15, Christoph Hellwig wrote:
> Currently all avr32 and sparc64 don't support kretprobes unlike all
> other kprobes supporting architectures. This is not nice from the
> user interface point of view and from the ugly ifdefs point of view.
> Is there a reason these ports
Neil Brown wrote:
On Saturday March 31, [EMAIL PROTECTED] wrote:
hi list!
in short:
I created a partitioned raid6 array with 2 missing drives. Now, I want to add a
device. It fails with:
flockmock ~ # mdadm -a /dev/md_d4 /dev/sdb2
mdadm: add new device failed for /dev/sdb2 as 4: Invalid
On Sat, 2007-03-31 at 01:31 -0700, Chris Wright wrote:
> This series converts x86_64 timers to clockevents drivers
> and then enables dynticks. There's some minor cleanups along
> the way. The lapic broadcast mechanism is untested, I'm sure it
> still needs work, there's still some cruft in
>Remove artificial maximum 256 loop device that can be created due to a
>legacy device number limit. Searching through lkml archive, there are
>several instances where users complained about the artificial limit
>that the loop driver impose. There is no reason to have such limit.
Hey, i was one
On Sat, 2007-03-31 at 13:09 -0700, Davide Libenzi wrote:
> +/*
> + * This gets called when the timer event triggers. We increment the
> + * tick count and wake the possible waiters. If the timer in a
> + * sequential one (->tintv.tv64 != 0), we re-arm it with hrtimer_forward().
> + */
> +static
On Sat, 31 Mar 2007, Dan Engel wrote:
> This patch is really being offered because it's what's needed to make the
> operation
> of the Belkin Flip USB KVM switch avaiable to user-space programs through the
> HID input
> event interface. The Belkin Flip KVM overloads LED usages to give software
On Sat, 2007-03-31 at 22:23 -0700, [EMAIL PROTECTED] wrote:
> The patch titled
> clocksource: driver initialize list value
> has been added to the -mm tree. Its filename is
> clocksource-driver-initialize-list-value.patch
>
> *** Remember to use Documentation/SubmitChecklist when
The xmm space on x86_64 is 256 bytes.
Signed-off-by: Avi Kivity <[EMAIL PROTECTED]>
diff --git a/include/asm-x86_64/processor.h b/include/asm-x86_64/processor.h
index 76552d7..90eb24e 100644
--- a/include/asm-x86_64/processor.h
+++ b/include/asm-x86_64/processor.h
@@ -201,7 +201,7 @@ struct
- kobject_add(>kobj);
+ if (kobject_add(>kobj)) {
+ kfree(p);
+ return;
Please add a printk warning before the return statement to log a
proper warning stating what happened, which file and line etc. That
way people can know why something did not work as
> Subject: after resume: X hangs after drawing a couple of windows
> workaround: clocksource=acpi_pm
> References : http://lkml.org/lkml/2007/3/8/117
> http://lkml.org/lkml/2007/3/25/20
> http://lkml.org/lkml/2007/3/26/151
> Submitter : Michael S.
Hi again,
After applying changes manually to 2.6.20.4 according to the link that
Steven sent I still get those errors (attached below) but no crash so
far.
I am wondering if its ok or having errors still will cause freezes.
Thanks in advance,
Apr 1 04:23:49 UFR2 kernel: CIFS VFS:
ROUND_UP macro cleanup, use ALIGN where ever appropriate
Signed-off-by: Milind Arun Choudhary <[EMAIL PROTECTED]>
---
hpux/fs.c |5 ++---
kernel/sys_parisc32.c |3 +--
2 files changed, 3 insertions(+), 5 deletions(-)
diff --git a/arch/parisc/hpux/fs.c
On 3/31/07, Gene Heskett <[EMAIL PROTECTED]> wrote:
This effect I have isolated down to something in the 31 patches from
2.6.20.4 to 2.6.20.5-rc1, but I'm going to need additional guidance in
setting up the bisect to find it. If indeed its a kernel problem.
First, set up a *small* test case,
Since kobject_add, sysfs_create_link and sysfs_create_file are marked
as '__must_check', we must always check their return values.
Signed-off-by: Cong WANG <[EMAIL PROTECTED]>
---
--- linux-2.6.21-rc5-mm3/fs/partitions/check.c.orig 2007-03-30
21:35:45.0 +0800
+++
On Sun, 1 Apr 2007 00:15:06 -0700 (PDT) Christoph Lameter <[EMAIL PROTECTED]>
wrote:
> On Sat, 31 Mar 2007, Andrew Morton wrote:
>
> > Yes, I think this is a flase positive - we'll never touch initkmem_list3[]
> > after free_initmem() because of the transitions of g_cpucache_up.
>
> Correct.
>
On Sat, 31 Mar 2007, Andrew Morton wrote:
> Yes, I think this is a flase positive - we'll never touch initkmem_list3[]
> after free_initmem() because of the transitions of g_cpucache_up.
Correct.
> (In which case set_up_list3s() shoud be __init, too?)
Correct. Its only called during slab
Spare Virtual: Virtual Memmap support for SPARSEMEM
SPARSEMEM is a pretty nice framework that unifies quite a bit of
code over all the arches. It would be great if it could be the default
so that we can get rid of various forms of DISCONTIG and other variations
on memory maps. So far what has
x86_64 make SPARSE_VIRTUAL the default
x86_64 is using 2M page table entries to map its 1-1 kernel space.
We implement the virtual memmap also using 2M page table entries.
So there is no difference at all to FLATMEM. Both schemes require
a page table and a TLB.
Thus the SPARSEMEM becomes the
Argh. This should have been Patch 2/2. There is nothing in between.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at
Spare Virtual: Virtual Memmap support for SPARSEMEM
SPARSEMEM is a pretty nice framework that unifies quite a bit of
code over all the arches. It would be great if it could be the default
so that we can get rid of various forms of DISCONTIG and other variations
on memory maps. So far what has
x86_64 make SPARSE_VIRTUAL the default
x86_64 is using 2M page table entries to map its 1-1 kernel space.
We implement the virtual memmap also using 2M page table entries.
So there is no difference at all to FLATMEM. Both schemes require
a page table and a TLB.
Thus the SPARSEMEM becomes the
Argh. This should have been Patch 2/2. There is nothing in between.
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at
On Sat, 31 Mar 2007, Andrew Morton wrote:
Yes, I think this is a flase positive - we'll never touch initkmem_list3[]
after free_initmem() because of the transitions of g_cpucache_up.
Correct.
(In which case set_up_list3s() shoud be __init, too?)
Correct. Its only called during slab
On Sun, 1 Apr 2007 00:15:06 -0700 (PDT) Christoph Lameter [EMAIL PROTECTED]
wrote:
On Sat, 31 Mar 2007, Andrew Morton wrote:
Yes, I think this is a flase positive - we'll never touch initkmem_list3[]
after free_initmem() because of the transitions of g_cpucache_up.
Correct.
(In
Since kobject_add, sysfs_create_link and sysfs_create_file are marked
as '__must_check', we must always check their return values.
Signed-off-by: Cong WANG [EMAIL PROTECTED]
---
--- linux-2.6.21-rc5-mm3/fs/partitions/check.c.orig 2007-03-30
21:35:45.0 +0800
+++
ROUND_UP macro cleanup, use ALIGN where ever appropriate
Signed-off-by: Milind Arun Choudhary [EMAIL PROTECTED]
---
hpux/fs.c |5 ++---
kernel/sys_parisc32.c |3 +--
2 files changed, 3 insertions(+), 5 deletions(-)
diff --git a/arch/parisc/hpux/fs.c
On 3/31/07, Gene Heskett [EMAIL PROTECTED] wrote:
This effect I have isolated down to something in the 31 patches from
2.6.20.4 to 2.6.20.5-rc1, but I'm going to need additional guidance in
setting up the bisect to find it. If indeed its a kernel problem.
First, set up a *small* test case,
Hi again,
After applying changes manually to 2.6.20.4 according to the link that
Steven sent I still get those errors (attached below) but no crash so
far.
I am wondering if its ok or having errors still will cause freezes.
Thanks in advance,
Apr 1 04:23:49 UFR2 kernel: CIFS VFS:
Subject: after resume: X hangs after drawing a couple of windows
workaround: clocksource=acpi_pm
References : http://lkml.org/lkml/2007/3/8/117
http://lkml.org/lkml/2007/3/25/20
http://lkml.org/lkml/2007/3/26/151
Submitter : Michael S. Tsirkin
- kobject_add(p-kobj);
+ if (kobject_add(p-kobj)) {
+ kfree(p);
+ return;
Please add a printk warning before the return statement to log a
proper warning stating what happened, which file and line etc. That
way people can know why something did not work
The xmm space on x86_64 is 256 bytes.
Signed-off-by: Avi Kivity [EMAIL PROTECTED]
diff --git a/include/asm-x86_64/processor.h b/include/asm-x86_64/processor.h
index 76552d7..90eb24e 100644
--- a/include/asm-x86_64/processor.h
+++ b/include/asm-x86_64/processor.h
@@ -201,7 +201,7 @@ struct
On Sat, 2007-03-31 at 22:23 -0700, [EMAIL PROTECTED] wrote:
The patch titled
clocksource: driver initialize list value
has been added to the -mm tree. Its filename is
clocksource-driver-initialize-list-value.patch
*** Remember to use Documentation/SubmitChecklist when testing
On Sat, 31 Mar 2007, Dan Engel wrote:
This patch is really being offered because it's what's needed to make the
operation
of the Belkin Flip USB KVM switch avaiable to user-space programs through the
HID input
event interface. The Belkin Flip KVM overloads LED usages to give software
On Sat, 2007-03-31 at 13:09 -0700, Davide Libenzi wrote:
+/*
+ * This gets called when the timer event triggers. We increment the
+ * tick count and wake the possible waiters. If the timer in a
+ * sequential one (-tintv.tv64 != 0), we re-arm it with hrtimer_forward().
+ */
+static enum
Remove artificial maximum 256 loop device that can be created due to a
legacy device number limit. Searching through lkml archive, there are
several instances where users complained about the artificial limit
that the loop driver impose. There is no reason to have such limit.
Hey, i was one of
On Sat, 2007-03-31 at 01:31 -0700, Chris Wright wrote:
This series converts x86_64 timers to clockevents drivers
and then enables dynticks. There's some minor cleanups along
the way. The lapic broadcast mechanism is untested, I'm sure it
still needs work, there's still some cruft in
Neil Brown wrote:
On Saturday March 31, [EMAIL PROTECTED] wrote:
hi list!
in short:
I created a partitioned raid6 array with 2 missing drives. Now, I want to add a
device. It fails with:
flockmock ~ # mdadm -a /dev/md_d4 /dev/sdb2
mdadm: add new device failed for /dev/sdb2 as 4: Invalid
On Sat, March 31, 2007 15:15, Christoph Hellwig wrote:
Currently all avr32 and sparc64 don't support kretprobes unlike all
other kprobes supporting architectures. This is not nice from the
user interface point of view and from the ugly ifdefs point of view.
Is there a reason these ports can't
201 - 300 of 562 matches
Mail list logo
