From: Stephane Eranian <[EMAIL PROTECTED]>
Add a notifier mechanism to the low level idle loop. You can register a
callback function which gets invoked on entry and exit from the low level idle
loop. The low level idle loop is defined as the polling loop, low-power call,
or the mwait instructio
Am Montag, 12. Februar 2007 08:38 schrieb Andi Kleen:
> When a machine check event is detected (including a AMD RevF threshold
> overflow event) allow to run a "trigger" program. This allows user space
> to react to such events sooner.
Could this not be merged with other reporting mechanisms? Thi
From: Ingo Molnar <[EMAIL PROTECTED]>
Clean up sched_clock() on i686: it will use the TSC if available and falls
back to jiffies only if the user asked for it to be disabled via notsc or
the CPU calibration code didnt figure out the right cpu_khz.
This generally makes the scheduler timestamps mo
From: Venkatesh Pallipadi <[EMAIL PROTECTED]>
Handle these 32 bit perfmon counter MSR writes cleanly in oprofile.
Signed-off-by: Venkatesh Pallipadi <[EMAIL PROTECTED]>
Signed-off-by: Andi Kleen <[EMAIL PROTECTED]>
---
arch/i386/oprofile/op_model_ppro.c |9 +
1 file changed, 5 inse
From: Venkatesh Pallipadi <[EMAIL PROTECTED]>
Change i386 nmi handler to handle 32 bit perfmon counter MSR writes cleanly.
Signed-off-by: Venkatesh Pallipadi <[EMAIL PROTECTED]>
Signed-off-by: Andi Kleen <[EMAIL PROTECTED]>
---
arch/i386/kernel/nmi.c | 64
From: Rene Herman <[EMAIL PROTECTED]>
A while ago it was remarked on list here that keeping the kernel 4M
aligned physically might be a performance win if the added 1M (it
normally loads at 1M) meant it would fit on one 4M aligned hugepage
instead of 2 and since that time I've been doing such.
From: Venkatesh Pallipadi <[EMAIL PROTECTED]>
P6 CPUs and Core/Core 2 CPUs which has 'architectural perf mon' feature,
only supports write of low 32 bits in Performance Monitoring Counters.
Bits 32..39 are sign extended based on bit 31 and bits 40..63 are reserved
and should be zero.
This patch
From: Glauber de Oliveira Costa <[EMAIL PROTECTED]>
This is a tiny cleanup to increase readability
Signed-off-by: Glauber de Oliveira Costa <[EMAIL PROTECTED]>
Signed-off-by: Andi Kleen <[EMAIL PROTECTED]>
Cc: Andi Kleen <[EMAIL PROTECTED]>
Signed-off-by: Andrew Morton <[EMAIL PROTECTED]>
---
From: Glauber de Oliveira Costa <[EMAIL PROTECTED]>
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 PROTECTED]>
Signed-off-
From: Adrian Bunk <[EMAIL PROTECTED]>
Every file should include the headers containing the prototypes for
it's global functions.
Signed-off-by: Adrian Bunk <[EMAIL PROTECTED]>
Signed-off-by: Andrew Morton <[EMAIL PROTECTED]>
Signed-off-by: Andi Kleen <[EMAIL PROTECTED]>
---
arch/i386/kernel/c
From: Rohit Seth <[EMAIL PROTECTED]>
This patch resolves the issue of running with numa=fake=X on kernel command
line on x86_64 machines that have big IO hole. While calculating the size
of each node now we look at the total hole size in that range.
Previously there were nodes that only had IO
From: Rene Herman <[EMAIL PROTECTED]>
Use adding __init to romsignature() (it's only called from probe_roms()
which is itself __init) as an excuse to submit a pedantic cleanup.
Signed-off-by: Rene Herman <[EMAIL PROTECTED]>
Signed-off-by: Andi Kleen <[EMAIL PROTECTED]>
Cc: Andi Kleen <[EMAIL PRO
From: Giuliano Procida <[EMAIL PROTECTED]>
[MTRR] fix 32-bit ioctls on x64_32
Signed-off-by: Giuliano Procida <[EMAIL PROTECTED]>
Signed-off-by: Andi Kleen <[EMAIL PROTECTED]>
---
Fixed incomplete support for 32-bit compatibility ioctls in
2.6.19.1. They were unhandled in one of three case-stat
Should be harmless because there is normally no memory there, but
technically it was incorrect.
Pointed out by Leo Duran
Signed-off-by: Andi Kleen <[EMAIL PROTECTED]>
---
arch/x86_64/kernel/pci-gart.c |4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
Index: linux/arch/x86_64/kernel
From: Randy Dunlap <[EMAIL PROTECTED]>
Fix typos.
Lots of whitespace changes for readability and consistency.
Signed-off-by: Randy Dunlap <[EMAIL PROTECTED]>
Signed-off-by: Andi Kleen <[EMAIL PROTECTED]>
---
Documentation/x86_64/boot-options.txt | 27 ++-
Documentatio
From: Zachary Amsden <[EMAIL PROTECTED]>
Initialize FS and GS to __KERNEL_DS as well. The actual value of them is not
important, but it is important to reload them in protected mode. At this time,
they still retain the real mode values from initial boot. VT disallows
execution of code under su
The symbol is needed to manipulate page tables, and modules shouldn't
do that.
Leftover from 2.4, but no in tree module should need it now.
Signed-off-by: Andi Kleen <[EMAIL PROTECTED]>
---
arch/x86_64/kernel/setup64.c |1 -
1 file changed, 1 deletion(-)
Index: linux/arch/x86_64/kernel/se
From: "Josef 'Jeff' Sipek" <[EMAIL PROTECTED]>
Signed-off-by: Josef 'Jeff' Sipek <[EMAIL PROTECTED]>
Signed-off-by: Andi Kleen <[EMAIL PROTECTED]>
---
include/asm-x86_64/io.h |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
Index: linux/include/asm-x86_64/io.h
==
From: Alexey Dobriyan <[EMAIL PROTECTED]>
Byte-to-byte identical /proc/apm here.
Signed-off-by: Alexey Dobriyan <[EMAIL PROTECTED]>
Signed-off-by: Andi Kleen <[EMAIL PROTECTED]>
---
arch/i386/kernel/apm.c | 26 ++
1 file changed, 18 insertions(+), 8 deletions(-)
Inde
From: Alexey Dobriyan <[EMAIL PROTECTED]>
It will execure cpuid only on the cpu we need.
Signed-off-by: Alexey Dobriyan <[EMAIL PROTECTED]>
Signed-off-by: Andi Kleen <[EMAIL PROTECTED]>
---
arch/i386/kernel/cpuid.c |7 ++-
1 file changed, 2 insertions(+), 5 deletions(-)
Index: linux/a
- Remove outdated comment
- Use cpu_relax() in a busy loop
Signed-off-by: Andi Kleen <[EMAIL PROTECTED]>
---
arch/i386/kernel/smp.c |5 ++---
1 file changed, 2 insertions(+), 3 deletions(-)
Index: linux/arch/i386/kernel/smp.c
From: Nicolas Kaiser <[EMAIL PROTECTED]>
Some typos in Kconfig.
Signed-off-by: Nicolas Kaiser <[EMAIL PROTECTED]>
Signed-off-by: Andi Kleen <[EMAIL PROTECTED]>
---
---
arch/x86_64/Kconfig | 12 ++--
1 file changed, 6 insertions(+), 6 deletions(-)
Index: linux/arch/x86_64/Kconfig
===
From: "Jan Beulich" <[EMAIL PROTECTED]>
Function is dead.
Signed-off-by: Jan Beulich <[EMAIL PROTECTED]>
Signed-off-by: Andi Kleen <[EMAIL PROTECTED]>
---
include/asm-x86_64/pgalloc.h |5 -
1 file changed, 5 deletions(-)
Index: linux/include/asm-x86_64/pgalloc.h
===
From: Jeff Garzik <[EMAIL PROTECTED]>
x86-64 is missing these:
Signed-off-by: Jeff Garzik <[EMAIL PROTECTED]>
Signed-off-by: Andi Kleen <[EMAIL PROTECTED]>
---
include/asm-x86_64/dma-mapping.h |3 +++
1 file changed, 3 insertions(+)
Index: linux/include/asm-x86_64/dma-mapping.h
==
When a machine check event is detected (including a AMD RevF threshold
overflow event) allow to run a "trigger" program. This allows user space
to react to such events sooner.
The trigger is configured using a new trigger entry in the
machinecheck sysfs interface. It is currently shared between
We trust the e820 table, so explicitely reserving ROMs shouldn't
be needed.
Signed-off-by: Andi Kleen <[EMAIL PROTECTED]>
---
arch/x86_64/kernel/setup.c | 130 -
1 file changed, 2 insertions(+), 128 deletions(-)
Index: linux/arch/x86_64/kernel/setu
From: "H. Peter Anvin" <[EMAIL PROTECTED]>
All Transmeta CPUs ever produced have constant-rate TSCs.
Signed-off-by: H. Peter Anvin <[EMAIL PROTECTED]>
Signed-off-by: Andi Kleen <[EMAIL PROTECTED]>
Cc: Andi Kleen <[EMAIL PROTECTED]>
Signed-off-by: Andrew Morton <[EMAIL PROTECTED]>
---
arch/i386
When calling into the EFI firmware, the parameters need to be passed on
the stack. The recent change to use -mregparm=3 breaks x86 EFI support.
This patch is needed to allow the new Intel-based Macs to suspend to ram
(efi.get_time is called during the suspend phase).
Signed-off-by: Frederic Riss
From: "Jan Beulich" <[EMAIL PROTECTED]>
while debugging an unrelated problem in Xen, I noticed odd reads from
non-existent MSRs. Having now found time to look why these happen, I
came up with below patch, which
- prevents accessing MCi_MISCj with j > 0 when the block pointer in
MCi_MISC0 is zero
From: Muli Ben-Yehuda <[EMAIL PROTECTED]>
- set bad_dma_address explicitly to 0x0
- reserve 32 pages from bad_dma_address and up
- WARN_ON() a driver feeding us bad_dma_address
Thanks to Leo Duran <[EMAIL PROTECTED]> for the suggestion.
Signed-off-by: Muli Ben-Yehuda <[EMAIL PROTECTED]>
Signed-
From: "Jan Beulich" <[EMAIL PROTECTED]>
Remove all parameters from this function that aren't really variable.
Signed-off-by: Jan Beulich <[EMAIL PROTECTED]>
Signed-off-by: Andi Kleen <[EMAIL PROTECTED]>
---
arch/i386/mm/fault.c | 18 --
arch/x86_64/mm/fault.c | 18
From: Ingo Molnar <[EMAIL PROTECTED]>
During kernel bootup, a new T60 laptop (CoreDuo, 32-bit) hangs about
10%-20% of the time in acpi_init():
Calling initcall 0xc055ce1a: topology_init+0x0/0x2f()
Calling initcall 0xc055d75e: mtrr_init_finialize+0x0/0x2c()
Calling initcall 0xc05664f3: param_s
From: "Andreas Herrmann" <[EMAIL PROTECTED]>
mtrr: fix size_or_mask and size_and_mask
This fixes two bugs in /proc/mtrr interface:
o If physical address size crosses the 44 bit boundary
size_or_mask is evaluated wrong.
o size_and_mask limits width of physical base
address for an MTRR to be le
From: Jack Steiner <[EMAIL PROTECTED]>
Add failsafe mechanism to HPET/TSC clock calibration.
Signed-off-by: Jack Steiner <[EMAIL PROTECTED]>
Updated to include failsafe mechanism & additional community feedback.
Patch built on latest 2.6.20-rc4-mm1 tree.
Signed-off-by: Andi K
This means if an illegal value is set for the segment registers there
ptrace will error out now with an errno instead of silently ignoring
it.
Signed-off-by: Andi Kleen <[EMAIL PROTECTED]>
---
arch/x86_64/kernel/ptrace.c |8 ++--
1 file changed, 6 insertions(+), 2 deletions(-)
Index: l
From: Alexey Dobriyan <[EMAIL PROTECTED]>
There was OpenVZ specific bug rendering some cpufreq drivers unusable
on SMP. In short, when cpufreq code thinks it confined itself to
needed cpu by means of set_cpus_allowed() to execute rdmsr, some
"virtual cpu" feature can migrate process to anywhere. T
From: Randy Dunlap <[EMAIL PROTECTED]>
List x86_64 quilt tree in MAINTAINERS.
Signed-off-by: Randy Dunlap <[EMAIL PROTECTED]>
Signed-off-by: Andi Kleen <[EMAIL PROTECTED]>
---
MAINTAINERS |1 +
1 file changed, 1 insertion(+)
Index: linux/MAINTAINERS
===
From: Alexey Dobriyan <[EMAIL PROTECTED]>
It will execute rdmsr and wrmsr only on the cpu we need.
Signed-off-by: Alexey Dobriyan <[EMAIL PROTECTED]>
Signed-off-by: Andi Kleen <[EMAIL PROTECTED]>
---
arch/i386/kernel/msr.c | 13 -
1 file changed, 4 insertions(+), 9 deletions(-)
From: Vivek Goyal <[EMAIL PROTECTED]>
o init() is a non __init function in .text section but it calls many
functions which are in .init.text section. Hence MODPOST generates lots
of cross reference warnings on i386 if compiled with CONFIG_RELOCATABLE=y
WARNING: vmlinux - Section mismatch: re
From: Vivek Goyal <[EMAIL PROTECTED]>
o Entry startup_32 was in .text section but it was accessing some init
data too and it prompts MODPOST to generate compilation warnings.
WARNING: vmlinux - Section mismatch: reference to .init.data:boot_params from
.text between '_text' (at offset 0xc01000
On Wed, Feb 07, 2007 at 09:32:54AM +0100, Christoph Hellwig wrote:
> On Wed, Feb 07, 2007 at 07:59:18AM +, Linux Kernel Mailing List wrote:
> > [IA64] swiotlb abstraction (e.g. for Xen)
> >
> > Add abstraction so that the file can be used by environments other than
> > IA64
> >
On Monday 12 February 2007 18:10, malc wrote:
> On Mon, 12 Feb 2007, Con Kolivas wrote:
> > Lots of confusion comes from this, and often people think their pc
> > suddenly uses a lot less cpu when they change from 1000HZ to 100HZ and
> > use this as an argument/reason for changing to 100HZ when in
On Mon, 2007-02-12 at 07:49 +0100, Andi Kleen wrote:
> On Sunday 11 February 2007 22:35, Benjamin Herrenschmidt wrote:
>
> > I'd like to have that on ppc as well, so I'd rather keep it in drivers/
>
> This will need some abstraction at least -- there are some early mapping hacks
> that are x86 sp
Is it possible to get file access time in millisecond resolution?
stat() returns time in seconds, but gettimeofday() can returns microseconds.
Thanks,
Jeff.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo inf
On Mon, 2007-02-12 at 06:32 +0100, Jens Axboe wrote:
> On Mon, Feb 12 2007, Rusty Russell wrote:
> > On Mon, 2007-02-12 at 05:43 +0100, Jens Axboe wrote:
> > > Here you map the entire request (lets call that segment A..Z), but
> > > end_request() only completes the first chunk of the request. So
>
Any comments on this blackfin arch kernel patch for 2.6.20?
We fixed a lot of issues according to the feedback against our last
patch for 2.6.18. We really appreciate your comments on this new one.
Thanks
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a m
On Mon, 12 Feb 2007, Con Kolivas wrote:
On Monday 12 February 2007 16:54, malc wrote:
On Mon, 12 Feb 2007, Con Kolivas wrote:
On 12/02/07, Vassili Karpov <[EMAIL PROTECTED]> wrote:
[..snip..]
The kernel looks at what is using cpu _only_ during the timer
interrupt. Which means if your HZ is
On Sat, Feb 10, 2007 at 07:54:00PM -0500, Dave Jones wrote:
>
> Whilst on the subject of RELATIME, is there any good reason why
> not to make this a default mount option ?
Ubuntu has been shipping with noatime as the default for some time
now, with no obvious problems (I'm running Ubuntu). I see
On Mon, 12 Feb 2007, Con Kolivas wrote:
On 12/02/07, Vassili Karpov <[EMAIL PROTECTED]> wrote:
[..snip..]
The kernel looks at what is using cpu _only_ during the timer
interrupt. Which means if your HZ is 1000 it looks at what is running
at precisely the moment those 1000 timer ticks occur.
On Sat, Feb 10, 2007 at 09:56:07AM -0800, Michael Kerrisk wrote:
> Val,
>
> I'm just updating the mount(2) man page for MS_RELATIME, and this is the
> text I've come up with:
>
>MS_RELATIME(Since Linux 2.6.20)
> When a file on this file system is accessed, only
>
On Sunday 11 February 2007 22:35, Benjamin Herrenschmidt wrote:
> I'd like to have that on ppc as well, so I'd rather keep it in drivers/
This will need some abstraction at least -- there are some early mapping hacks
that are x86 specific right now.
> I agree that it doesn't need to be a module.
ris wrote:
procs ---memory-- ---swap-- -io -system-- cpu
r b swpd free buff cache si sobibo in cs us sy id wa
0 0 0 303444 53224 36013200 276 157 627 814 5 2 89 4
0 0 0 302956 53228 36033200 196
On Mon, 2007-02-12 at 15:43 +0900, Ian Kent wrote:
> On Thu, 2007-02-08 at 11:33 +0900, Ian Kent wrote:
> > On Wed, 2007-02-07 at 19:18 +0100, Olivier Galibert wrote:
> > > On Thu, Feb 08, 2007 at 03:07:41AM +0900, Ian Kent wrote:
> > > > It may be better to update to a later kernel so I don't have
Please test the attached patch over 2.6.20.
Thanks.
--
tejun
diff --git a/drivers/ata/libata-core.c b/drivers/ata/libata-core.c
index 667acd2..d6fcf0a 100644
--- a/drivers/ata/libata-core.c
+++ b/drivers/ata/libata-core.c
@@ -1478,7 +1478,16 @@ int ata_dev_read_id(struct ata_device *dev, unsigne
Hello, Paul.
Paul Rolland wrote:
This looks like the problems that hopefully the patches
from Tejun and
from Mark Lord cured (the delay after reset and the task file clear)
Any chance I can find this patch(es) and try them ?
Also, I've seen a :
ata1: Spurious SDB FIS during NCQ issue=0x0
On Thu, 2007-02-08 at 11:33 +0900, Ian Kent wrote:
> On Wed, 2007-02-07 at 19:18 +0100, Olivier Galibert wrote:
> > On Thu, Feb 08, 2007 at 03:07:41AM +0900, Ian Kent wrote:
> > > It may be better to update to a later kernel so I don't have to port the
> > > patch to several different kernels. Is t
Jeff Garzik wrote:
> Tobias Diedrich wrote:
> >Tobias Diedrich wrote:
> >>Ayaz Abdulla wrote:
> >>>For all those who are having issues, please try out the attached patch.
> >>Will try.
> >
> >Does not apply cleanly against 2.6.20, is this one fixed up right?
>
> It probably needs to be top of 2.6.
On Sun, Feb 11 2007, Paul E. McKenney wrote:
> This patch optimizes the "quick" RCU update-side fastpath, so that in the
> absence of readers, synchronize_qrcu() does four non-atomic comparisons
> and three memory barriers, eliminating the need to acquire the global
> lock in this case. Lightly te
On Sun, Feb 11, 2007 at 10:47:27AM -0800, Greg KH wrote:
> It's in my queue and is on track to get in before 2.6.21-rc1 is out.
It breaks the build for everyone, please fast-forward the merging of
this.
Jeff
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
t
On Sat, Feb 10, 2007 at 05:41:13PM +0100, Adrian Bunk wrote:
> New drivers since 2.6.16.39:
> - Areca ARC11X0/ARC12X0 SATA-RAID support
> - AMD Athlon64/FX and Opteron temperature sensor
Sorry - I think I just sent a blank reply to this! Oops.
I was going to say - thanks. We'll definitely be us
On Monday 12 February 2007 16:54, malc wrote:
> On Mon, 12 Feb 2007, Con Kolivas wrote:
> > On 12/02/07, Vassili Karpov <[EMAIL PROTECTED]> wrote:
>
> [..snip..]
>
> > The kernel looks at what is using cpu _only_ during the timer
> > interrupt. Which means if your HZ is 1000 it looks at what is run
On Sat, Feb 10, 2007 at 05:41:13PM +0100, Adrian Bunk wrote:
> New drivers since 2.6.16.39:
> - Areca ARC11X0/ARC12X0 SATA-RAID support
> - AMD Athlon64/FX and Opteron temperature sensor
>
>
> Location:
> ftp://ftp.kernel.org/pub/linux/kernel/v2.6/
>
> git tree:
> git://git.kernel.org/pub/scm/li
On Monday 12 February 2007 16:55, Stephen Rothwell wrote:
> On Mon, 12 Feb 2007 16:44:22 +1100 "Con Kolivas" <[EMAIL PROTECTED]> wrote:
> > The kernel looks at what is using cpu _only_ during the timer
> > interrupt. Which means if your HZ is 1000 it looks at what is running
> > at precisely the mo
On Mon, 12 Feb 2007 16:44:22 +1100 "Con Kolivas" <[EMAIL PROTECTED]> wrote:
>
> The kernel looks at what is using cpu _only_ during the timer
> interrupt. Which means if your HZ is 1000 it looks at what is running
> at precisely the moment those 1000 timer ticks occur. It is
> theoretically possibl
AUTH_UNIX authentication (the standard with NFS) has a limit of 16
groups ids. This causes problems for people in more than 16
groups.
So allow the server to map a uid into a list of group ids based on
local knowledge rather depending on the (possibly truncated) list
from the client.
If there i
Following are 4 patchs from knfsd suitable for 2.6.21.
Numbers 3 and 4 provide new usability features that require a new
nfs-utils to make full use of (all nfs-utils will ofcourse continue to
work providing the functionality it always provided).
(3) allows a 16 byte uuid to be used to identify th
If we are using the same version/fsid as a current filehandle, then
there is no need to verify the the numbers are valid for this
export, and they must be (we used them to find this export).
This allows us to simplify the fsid selection code.
Also change "ref_fh_version" and "ref_fh_fsid_type" t
Add support for using a filesystem UUID to identify and
export point in the filehandle.
For NFSv2, this UUID is xor-ed down to 4 or 8 bytes so
that it doesn't take up too much room. For NFSv3+, we
use the full 16 bytes, and possibly also a 64bit inode number
for exports beneath the root of a file
Most files in the 'nfsd' filesystem are transactional.
When you write, a reply is generated that can be read back
only on the same 'file'.
If the reply has zero length, the 'write' will incorrectly
return a value of '0' instead of the length that was
written. This causes 'rpc.nfsd' to give an an
Robert Hancock wrote:
Given the above, what I'm proposing to do is:
-Remove the blacklisting of Maxtor BANC1G10 firmware for FUA. If we need
to FUA-blacklist any drives this should likely be added to the existing
"horkage" mechanism we now have. However, at this point I don't think
that's nee
On 12/02/07, Vassili Karpov <[EMAIL PROTECTED]> wrote:
Hello,
How does the kernel calculates the value it places in `/proc/stat' at
4th position (i.e. "idle: twiddling thumbs")?
For background information as to why this question arose in the first
place read on.
While writing the code dealing
Hello,
How does the kernel calculates the value it places in `/proc/stat' at
4th position (i.e. "idle: twiddling thumbs")?
For background information as to why this question arose in the first
place read on.
While writing the code dealing with video acquisition/processing at
work noticed that wh
On Mon, Feb 12 2007, Jens Axboe wrote:
> On Mon, Feb 12 2007, Rusty Russell wrote:
> > On Mon, 2007-02-12 at 05:43 +0100, Jens Axboe wrote:
> > > On Mon, Feb 12 2007, Rusty Russell wrote:
> > > > + end_request(bd->req, bd->lb_page->result == 1);
> > >
> > > You are using the old-style end req
On Mon, Feb 12 2007, Rusty Russell wrote:
> On Mon, 2007-02-12 at 05:43 +0100, Jens Axboe wrote:
> > On Mon, Feb 12 2007, Rusty Russell wrote:
> > > + end_request(bd->req, bd->lb_page->result == 1);
> >
> > You are using the old-style end request handling. So while I generally
> > discourage use of
On ia64, drivers/base/dma-mapping.c doesn't build because it calls
dma_alloc_noncoherent() and dma_free_noncoherent(), which appear to be
terminally broken; the calls end up generating errors like
drivers/base/dma-mapping.c: In function 'dmam_noncoherent_release':
drivers/base/dma-mapping.
On Mon, 2007-02-12 at 05:43 +0100, Jens Axboe wrote:
> On Mon, Feb 12 2007, Rusty Russell wrote:
> > + end_request(bd->req, bd->lb_page->result == 1);
>
> You are using the old-style end request handling. So while I generally
> discourage use of end_request(), you seem to have a bigger problem he
On Mon, Feb 12, 2007 at 12:26:52AM +, Alan wrote:
> > Unless I'm mistaken, I have to type the passphrase twice then :
> > - once at suspend
> > - once at resume
> >
> > which is once more per "boot" than what I'm doing on loop-aes.
>
> You don't need to type in a key at suspend time if yo
Zwane Mwaikambo <[EMAIL PROTECTED]> writes:
> On Sun, 11 Feb 2007, Eric W. Biederman wrote:
>
>> > 2.15.2 PCI Express* Legacy INTx Support and Boot Interrupt
>> > http://download.intel.com/design/chipsets/datashts/30262802.pdf
>>
>> Ouch. And this kind of thing isn't exactly uncommon.
>>
>> How
This patch optimizes the "quick" RCU update-side fastpath, so that in the
absence of readers, synchronize_qrcu() does four non-atomic comparisons
and three memory barriers, eliminating the need to acquire the global
lock in this case. Lightly tested. Algorithm has been validated for
the 3-reader-
On Mon, Feb 12 2007, Rusty Russell wrote:
> +static irqreturn_t lgb_irq(int irq, void *_bd)
> +{
> + struct blockdev *bd = _bd;
> + unsigned long flags;
> +
> + if (!bd->req) {
> + pr_debug("No work!\n");
> + return IRQ_NONE;
> + }
> +
> + if (!bd->lb_pag
Howdy!
On Mon, 2007-02-12 at 01:10 +0100, Tilman Schmidt wrote:
> Hi,
>
> Am 11.02.2007 23:37 schrieb Nigel Cunningham:
> > On Sun, 2007-02-11 at 00:45 +0100, Tilman Schmidt wrote:
> >> Am 10.02.2007 23:37 schrieb Nigel Cunningham:
> >>> If your device requires power management, and you know it r
A simple block driver for lguest (/dev/lgbX). Only does one request
at once.
Signed-off-by: Rusty Russell <[EMAIL PROTECTED]>
===
--- a/drivers/block/Makefile
+++ b/drivers/block/Makefile
@@ -28,4 +28,5 @@ obj-$(CONFIG_VIODASD)
Fairly complete documentation for lguest. I actually want to get rid
of the "coding" part of lguest.txt and roll it into the code itself,
literary-programming-style.
The launcher utility is also here: I don't have delusions of interface
stability, so it makes sense to have it here as an example,
A trivial driver to have a basic lguest console, using the hvc_console
infrastructure.
Signed-off-by: Rusty Russell <[EMAIL PROTECTED]>
diff -r aaa62bd9788a drivers/char/Makefile
--- a/drivers/char/Makefile Mon Feb 12 13:01:16 2007 +1100
+++ b/drivers/char/Makefile Mon Feb 12 13:01:45 200
This network driver operates both to the host process, and to other
guests. It's pretty trivial.
Signed-off-by: Rusty Russell <[EMAIL PROTECTED]>
===
--- a/drivers/net/Makefile
+++ b/drivers/net/Makefile
@@ -217,3 +217,4 @@ obj-$(CO
Finally, we put in the Makefile, so it will build.
Linking the switcher code (hypervisor.S) ready to be copied
into the top of memory is the only non-trivial thing here.
Signed-off-by: Rusty Russell <[EMAIL PROTECTED]>
===
--- a/arc
This is the guest code which replaces the parts of paravirt_ops with
hypercalls. It's fairly trivial. This patch also includes trivial
bus driver for lguest devices, and an extern declarations for boot_pda
(previously frobbed only from head.S).
Signed-off-by: Rusty Russell <[EMAIL PROTECTED]>
d
Unfortunately, we don't have the build infrastructure for "private"
asm-offsets.h files, so there's a not-so-neat include in
arch/i386/kernel/asm-offsets.c.
The four headers are:
asm/lguest.h:
Things the guest needs to know (hypercall numbers, etc).
asm/lguest_device.h:
Things lgue
lguest uses the convenient futex infrastructure for inter-domain I/O,
so expose get_futex_key, get_key_refs (renamed get_futex_key_refs) and
drop_key_refs (renamed drop_futex_key_refs). Also means we need to
expose the union that these use.
No code changes.
Signed-off-by: Rusty Russell <[EMAIL P
lguest does some fairly lowlevel things to support a host, which
normal modules don't need:
math_state_restore:
When the guest triggers a Device Not Available fault, we need
to be able to restore the FPU
__put_task_struct:
We need to hold a reference to another task for in
Len Brown <[EMAIL PROTECTED]> said:
> Okay, but better to use disable_acpi()
> indeed, since this would be the first code not already inside CONFIG_ACPI
> to invoke disable_acpi(), we could define the inline as empty and you could
> then scratch the #ifdef too.
Signed-off-by: Rusty Russell <[EMAIL
When I implemented the DECLARE_PER_CPU(var) macros, I was careful that
people couldn't use "var" in a non-percpu context, by prepending
percpu__. I never considered that this would allow them to overload
the same name for a per-cpu and a non-percpu variable.
It is only one of many horrors in the
Extern declarations belong in headers. Times, they are a'changin.
Signed-off-by: Rusty Russell <[EMAIL PROTECTED]>
===
--- a/arch/i386/mm/discontig.c
+++ b/arch/i386/mm/discontig.c
@@ -101,7 +101,6 @@ extern void add_one_highpage_in
Allows external actors to disable mce.
Signed-off-by: Rusty Russell <[EMAIL PROTECTED]>
===
--- a/arch/i386/kernel/cpu/mcheck/mce.h
+++ b/arch/i386/kernel/cpu/mcheck/mce.h
@@ -1,4 +1,5 @@
#include
+#include
void amd_mcheck_init
There's a really nice console helper (esp. for virtual console
drivers) in drivers/char/hvc_console.c. It has only ever been used
for PowerPC, though, so it uses NO_IRQ which is only defined there.
Let's fix that so it's more widely useful. By, say, lguest.
Signed-off-by: Rusty Russell <[EMAIL
Whenever we schedule, __switch_to calls load_esp0 which does:
tss->esp0 = thread->esp0;
This is never initialized for the initial thread (ie "swapper"), so
when we're scheduling that, we end up setting esp0 to 0. This is
fine: the swapper never leaves ring 0, so this field is never used.
The current code simply calls "start_kernel" directly if we're under a
hypervisor and no paravirt_ops backend wants us, because paravirt.c
registers that as a backend.
This was always a vain hope; start_kernel won't get far without setup.
It's also impossible for paravirt_ops backends which don't
I've been looking at some list archives from about a year ago when there
was a big hoohah about FUA in libata. To summarize what I've gotten from
that discussion:
Nicolas Mailhot ran into a problem with the first kernels that supported
libata FUA, using a Silicon Image 3114 controller and a Ma
On Fri, Feb 09, 2007 at 07:36:40AM +, Russell King wrote:
> On Fri, Feb 09, 2007 at 02:48:42PM +1100, David Gibson wrote:
> > At present set_irq_handler() and all the existing variants take the
> > desc->lock for the irq in question before adjusting the irq's flow
> > handler. This can cause p
On Sun, Feb 11, 2007 at 05:08:17PM -0500, Tejun Heo wrote:
> Markus Trippelsdorf wrote:
> >This update breaks sata_via on my VIA K8T800Pro machine:
> >
> > sata_via :00:0f.0 : failed to iomap PCI BAR 0
> > sata_via :00:0f.0 : out of memory
> > sata_via probe of :00:0f.0 failed with err
1 - 100 of 314 matches
Mail list logo
