On Wed, Dec 19, 2007 at 08:40:32PM +0100, Ingo Molnar wrote:
>
> * H. Peter Anvin <[EMAIL PROTECTED]> wrote:
>
> > Ingo Molnar wrote:
> >> * Venki Pallipadi <[EMAIL PROTECTED]> wrote:
> >>
> >>> Aviod TLB flush IPIs during C3 states by voluntary leave_mm() before
> >>> entering C3.
> >>>
> >>>
The printk statements that result when the user does not have the
proper key available could use some refining.
Signed-off-by: Mike Halcrow <[EMAIL PROTECTED]>
---
diff --git a/fs/ecryptfs/crypto.c b/fs/ecryptfs/crypto.c
index f8ef0af..beba580 100644
--- a/fs/ecryptfs/crypto.c
+++
Hello All,
Back in August we had a discussion about the default priorities of
IRQ-threads and softirqs, and the lack of a mechanism to configure them from
within the kernel.
(see http://www.mail-archive.com/[EMAIL PROTECTED]/msg01022.html)
Here is a patchset that implements such a nice feature
This patch adds a generic routine to the kernel, so that a map of
settings can be entered on the kernel commandline.
Signed-off-by: Remy Bohmer <[EMAIL PROTECTED]>
---
---
include/linux/kernel.h |1
lib/cmdline.c | 58 +
2 files
The RT-patch originally creates all its IRQ-threads at priority 50.
Of course, this is not a usable default for many realtime systems
and therefor these priorities has to be tuneable for each RT-system.
But, currently there is no way within the kernel to adjust this to
the needs of the user. Some
The RT-patch originally creates all its softirq-threads at
priority 50. Of course, this is not a usable default for many
realtime systems and therefor these priorities has to be tuneable
for each RT-system. But, currently there is no way within the
kernel to adjust this to the needs of the user.
On Wed, 19 Dec 2007, Daniel Walker wrote:
> > It looks like the swsusp_save() calls drain_all_pages() , which calls
> > on_each_cpu() .. On return on_each_cpu() unconditionally enables
> > interrupts so the rest of the resume process has interrupt enable
> > (which , it looks like, shouldn't
Here is a so-called BUG when trying to insert the following
module into the kernel (2.6.22.1).
BUG: unable to handle kernel paging request at virtual address 6814ec83
printing eip:
c016d013
*pde =
Oops: [#1]
PREEMPT SMP
Modules linked in: MemDev parport_pc lp parport nfsd
On Wed, Dec 19, 2007 at 03:10:28PM -0500, linux-os (Dick Johnson) wrote:
>
>
> Here is a so-called BUG when trying to insert the following
> module into the kernel (2.6.22.1).
>
>
> BUG: unable to handle kernel paging request at virtual address 6814ec83
> printing eip:
> c016d013
> *pde =
Hi,
On Wed, 19 Dec 2007, Serge E. Hallyn wrote:
> > I assume you mean S_REVOKE_LOCK and not ->i_mutex, right?
>
> No I did mean the i_mutex since you take the i_mutex when you set
> S_REVOKE_LOCK. So between that and the comment above do_lookup(),
> I assumed you were trying to lock out
On Wed, Dec 19, 2007 at 11:48:14AM -0800, H. Peter Anvin wrote:
> Ingo Molnar wrote:
> >
> >i dont think it's required for C3 to even turn off any portion of the
> >CPU - if an interrupt arrives after the C3 sequence is initiated but
> >just before dirty cachelines have been flushed then the CPU
Quoting Pekka J Enberg ([EMAIL PROTECTED]):
> Hi,
>
> On Wed, 19 Dec 2007, Serge E. Hallyn wrote:
> > > I assume you mean S_REVOKE_LOCK and not ->i_mutex, right?
> >
> > No I did mean the i_mutex since you take the i_mutex when you set
> > S_REVOKE_LOCK. So between that and the comment above
On Wed, 2007-12-19 at 16:43 +0300, Ivan Kokshaysky wrote:
> On Wed, Dec 19, 2007 at 04:10:19PM +1100, Benjamin Herrenschmidt wrote:
> > This patch changes the x86 PCI code to disable IO and/or Memory
> > decoding on a PCI device when a resource of that type failed to
> > be allocated.
>
> Oh,
Hello,
> preempt-rt can disable interrupts for 300 us?
I am not sure if it really is an interrupt lock that long, but on
these ARM cores I still run into latencies that large. I tried using
latency_trace to figure out where they come from, but that tool even
reports interrupt locks up to 10 ms
On Dec 19 2007 15:10, linux-os (Dick Johnson) wrote:
>I got rid of __init and anything else that I thought could cause the fault,
I anticipate the day removing __init causes a breakage, heh.
I mean, if all in-tree modules and LDD3 use it, it can't be wrong, can it?
>plus got rid of all the
On Wed, Dec 19, 2007 at 03:10:28PM -0500, linux-os (Dick Johnson) wrote:
>
>
> Here is a so-called BUG when trying to insert the following
> module into the kernel (2.6.22.1).
>
>
> MODULE_ALIAS("MemDev");
> module_init(startup);
> module_exit(quit);
Just a wild guess. Your init and exit
Theodore Tso wrote:
On Sat, Dec 08, 2007 at 06:40:17PM -0600, Matt Mackall wrote:
I'm working on strengthening forward security for cases where the
internals are exposed to an attacker. There are any number of
situations where this can and does happen, and ensuring we don't
expose ourselves to
On 12/14/2007 08:11 PM, Gosney, JeremiX wrote:
> We've noticed the 2.6-based Linux systems in our test lab are
> experiencing some "ARP flux"-like symptoms.
>
> The systems reply with eth0's hardware address to all ARP requests,
> regardless of the IP being queried. Because of this, the system
On Wed, 19 Dec 2007 20:45:53 +0100 Remy Bohmer wrote:
> Documentation/kernel-parameters.txt |7 ++
> include/linux/irq.h |1
> kernel/irq/manage.c | 101
>
> 3 files changed, 98 insertions(+), 11 deletions(-)
>
>
FYI, your patch needed the fix below for !SMP. It works fine otherwise.
Ingo
---
include/asm-x86/mmu.h |6 ++
1 file changed, 6 insertions(+)
Index: linux/include/asm-x86/mmu.h
===
---
On Wed, 19 Dec 2007, Lennart Sorensen wrote:
> On Wed, Dec 19, 2007 at 03:10:28PM -0500, linux-os (Dick Johnson) wrote:
>>
>>
>> Here is a so-called BUG when trying to insert the following
>> module into the kernel (2.6.22.1).
>>
>>
>> BUG: unable to handle kernel paging request at virtual
On Wed, 19 Dec 2007 20:45:54 +0100 Remy Bohmer wrote:
> Documentation/kernel-parameters.txt | 11 +++
> kernel/softirq.c| 105
> ++--
> 2 files changed, 99 insertions(+), 17 deletions(-)
>
> Index:
On Mon, 2007-12-17 at 16:50 -0800, David Miller wrote:
> The problem is likely what device struct you are passing to
> dma_sync_single_for_device(), it has to be a real pci_dev or similar
> that has it's dev_archdata properly initialized.
>
> I bet dev_archdata in whatever "struct device" is
On Tue, 2007-12-18 at 11:38 +0100, Stefan Richter wrote:
> So, ohci->card.device is in fact _dev->dev.
>
> Also note:
> - The very same code did not oops at this point in 2.6.22. It only
> started doing so in 2.6.23.
> - There has been no other report of this kind for any other
>
On Wed, 19 Dec 2007 20:45:52 +0100 Remy Bohmer wrote:
> This patch adds a generic routine to the kernel, so that a map of
> settings can be entered on the kernel commandline.
>
> Signed-off-by: Remy Bohmer <[EMAIL PROTECTED]>
>
> ---
> ---
> include/linux/kernel.h |1
> lib/cmdline.c
On Wed, 19 Dec 2007, Jan Engelhardt wrote:
>
> On Dec 19 2007 15:10, linux-os (Dick Johnson) wrote:
>
>
>> I got rid of __init and anything else that I thought could cause the fault,
>
> I anticipate the day removing __init causes a breakage, heh.
> I mean, if all in-tree modules and LDD3 use
On Dec 19 2007 16:10, linux-os (Dick Johnson) wrote:
>> I anticipate the day removing __init causes a breakage, heh.
>> I mean, if all in-tree modules and LDD3 use it, it can't be wrong, can it?
>>
>>> plus got rid of all the code!
>>> static int32_t startup()
>>
>> I noticed that. Where's your
On Wed, 19 Dec 2007, Eric Dumazet wrote:
> James Nichols a écrit :
> > On 12/19/07, Eric Dumazet <[EMAIL PROTECTED]> wrote:
> > > James Nichols a écrit :
> > > > > So you see outgoing SYN packets, but no SYN replies coming from the
> > > > > remote
> > > > > peer ? (you mention ACKS, but the
Parag Warudkar wrote:
> On 12/19/07, Kok, Auke <[EMAIL PROTECTED]> wrote:
> [snip]
>
>> I can't possibly see any benefit from this other than that you just add up
>> to a
>> whole second to the initialization cycle, which is bad.
>>
> Well, Ok but it can't be bad - I've been using this patch
Hello Randy,
Sorry for the language errors, English is not my Native language, so I
make these stupid errors...
> > + * get_map_option - Parse integer from an option map
> The @param lines (below) need to go here, immediately following the
> function short description (the line above). No
From: Harvey Harrison <[EMAIL PROTECTED]>
[ [EMAIL PROTECTED]: updated it to latest x86.git ]
Factor common X86_32, X86_64 kprobe reenter logic from deeply
indented section to helper function.
Signed-off-by: Harvey Harrison <[EMAIL PROTECTED]>
Signed-off-by: Ingo Molnar <[EMAIL PROTECTED]>
Move some deeply indented code related to re-entrance processing
from kprobe_handler() to reenter_kprobe().
Signed-off-by: Masami Hiramatsu <[EMAIL PROTECTED]>
Cc: Ananth N Mavinakayanahalli <[EMAIL PROTECTED]>
Cc: Jim Keniston <[EMAIL PROTECTED]>
---
arch/x86/kernel/kprobes.c | 46
Fix a preemption bug in kprobe_handler(). It has to call preempt_enable()
before returning.
Signed-off-by: Masami Hiramatsu <[EMAIL PROTECTED]>
---
arch/x86/kernel/kprobes.c |3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
Index: b/arch/x86/kernel/kprobes.c
Since it was decided that low memory protection from userspace couldn't
be turned on by default add a Kconfig option to allow users/distros to
set a default at compile time. This value is still tunable after boot
in /proc/sys/vm/mmap_min_addr
Signed-off-by: Eric Paris <[EMAIL PROTECTED]>
---
Peter Zijlstra wrote:
Hi,
Another posting of the full swap over NFS series.
Andrew/Linus, could we start thinking of sticking this in -mm?
Two questions:
1 - what is the memory use impact on the system which don't do swap over
NFS, such as embedded systems, and
2 - what is the advantage
Theodore Tso wrote:
On Tue, Dec 18, 2007 at 02:39:00PM +1030, David Newall wrote:
Thus, the entropy saved at shutdown can be known at boot-time. (You can
examine the saved entropy on disk.)
If you can examine the saved entropy on disk, you can also introduce a
trojan horse kernel that logs
David Newall wrote:
Theodore Tso wrote:
On Tue, Dec 18, 2007 at 01:43:28PM +1030, David Newall wrote:
On a server, keyboard and mouse are rarely used. As you've described
it, that leaves only the disk, and during the boot process, disk
accesses and timing are somewhat predictable. Whether
On Wed, Dec 19, 2007 at 03:40:12PM +0100, Jean Delvare wrote:
> In general we keep the all-in-one alarms file for compatibility, but
> given that this driver is fairly new and libsensors never had specific
> support for it anyway, it's probably OK to drop it this time.
Thanks for the code review.
hfs seems prone to bad things when it encounters on disk corruption.
Many values are read from disk, and used as lengths to memcpy, as an
example. This patch fixes up several of these problematic cases.
o sanity check the on-disk maximum key lengths on mount
(these are set to a defined value
On Dec 19, 2007 4:38 PM, Kok, Auke <[EMAIL PROTECTED]> wrote:
> Parag Warudkar wrote:
> > On 12/19/07, Kok, Auke <[EMAIL PROTECTED]> wrote:
>
> why would this patch reduce wakeups even more than round_jiffies()? Does it
> make
> our ~2 second update interval not reliable? can you quantify "shows
Thank you very much for your response Clemens.
I tried strace on a regular system. It does not show which tty, etc., as it
uses the stdout (fd = 1) and write(1, ...) to it.
This is not a student project. I am trying to build my own kernel and ramdisk.
Kernel boots fine to a point where it
Parag Warudkar wrote:
> On Dec 19, 2007 4:38 PM, Kok, Auke <[EMAIL PROTECTED]> wrote:
>> Parag Warudkar wrote:
>>> On 12/19/07, Kok, Auke <[EMAIL PROTECTED]> wrote:
>> why would this patch reduce wakeups even more than round_jiffies()? Does it
>> make
>> our ~2 second update interval not
Linus, please pull the latest x86 git tree from:
git://git.kernel.org/pub/scm/linux/kernel/git/x86/linux-2.6-x86.git
5 fixes. Thanks!
Ingo
-->
Adrian Bunk (4):
x86 apic_32.c section fix
x86 smpboot_32.c section fixes
x86_32: select_idle_routine()
From: Stefan Richter <[EMAIL PROTECTED]>
Date: Wed, 19 Dec 2007 17:33:05 +0100
> drivers/firewire/fw_ohci.c needs them for dma_map_single() +
> dma_sync_single_for_device() in the pci_driver.probe(), sometime after
> it called pci_enable_device(), before finishing the probe.
I'll take a look at
On Wednesday, 19 of December 2007, Christoph Lameter wrote:
> On Wed, 19 Dec 2007, Daniel Walker wrote:
>
> > > It looks like the swsusp_save() calls drain_all_pages() , which calls
> > > on_each_cpu() .. On return on_each_cpu() unconditionally enables
> > > interrupts so the rest of the resume
On Wed, 19 Dec 2007 21:50:50 +0300
Anton Vorontsov <[EMAIL PROTECTED]> wrote:
> On Wed, Dec 19, 2007 at 01:02:41PM -0500, Andres Salomon wrote:
> [...]
> > > > Hm. It occurs to me that there's nothing keeping us from having a
> > > > single callback for the driver properties. Keeping the other
This driver also had that funny alarm1/alarm2 thing; here's a revision
of yesterday's patch with that straightened out.
---
This driver reports voltage, temperature and fan sensor readings
on an ADT7473 chip.
Signed-off-by: Darrick J. Wong <[EMAIL PROTECTED]>
---
drivers/hwmon/Kconfig | 10
On Wed, Dec 19, 2007 at 05:17:51PM -0500, [EMAIL PROTECTED] wrote:
> commit d1f2a573ca7083d237cfc354f42e089de9fa0f0b
> Author: Tony Camuso <[EMAIL PROTECTED]>
> Date: Wed Dec 19 15:33:53 2007 -0500
>
> Introduces a flag bit to arch/x86/pci/pci.h to indicate that
> MMCONFIG is the
On Wed, Dec 19, 2007 at 05:17:56PM -0500, [EMAIL PROTECTED] wrote:
> commit 307e3aecde8060af3802590f8c5bffb5456fe22b
> Author: Tony Camuso <[EMAIL PROTECTED]>
> Date: Wed Dec 19 15:38:31 2007 -0500
>
> Modifies arch/x86/pci/direct.c to add the Legacy PCI Config routines
> that will be
On Wed, Dec 19, 2007 at 05:18:06PM -0500, [EMAIL PROTECTED] wrote:
> commit ab28e1157e970f711c8451b66b3f940ec092db9d
> Author: Tony Camuso <[EMAIL PROTECTED]>
> Date: Wed Dec 19 15:51:48 2007 -0500
>
> Introduces the x86 arch-specific routine that will determine whether
> a device
On Wed, Dec 19, 2007 at 05:18:06PM -0500, [EMAIL PROTECTED] wrote:
> commit ab28e1157e970f711c8451b66b3f940ec092db9d
> Author: Tony Camuso <[EMAIL PROTECTED]>
> Date: Wed Dec 19 15:51:48 2007 -0500
>
> Introduces the x86 arch-specific routine that will determine whether
> a device
On Wed, Dec 19, 2007 at 05:17:46PM -0500, [EMAIL PROTECTED] wrote:
> OVERVIEW
> ===
>
> The patches should be applied in sequence to obviate any
> possible build problems.
>
> The patch-set was built against 2.6.24-rc5
>
> Description
> ===
>
> There exist devices that do not
On Thu, 20 Dec 2007, Rafael J. Wysocki wrote:
> > We could reexport drain_local_pages() again but then I do not understand
> > why we would only drain the pages of this processor and not of all other
> > processors as well. It seems that software suspend intend was to flush
> > them all right?
On Dec 19 2007 16:59, Eric Paris wrote:
>
>+config SECURITY_DEFAULT_MMAP_MIN_ADDR
>+int "Low address space to protect from user allocation"
Hm, should not this be 'hex'?
>+depends on SECURITY
>+default 0
>+help
--
To unsubscribe from this list: send the line
On Thursday 20 December 2007 00:45, Rik van Riel wrote:
> On Wed, 19 Dec 2007 11:56:48 +1100
>
> Nick Piggin <[EMAIL PROTECTED]> wrote:
> > On Wednesday 19 December 2007 08:15, Rik van Riel wrote:
> > > Rework of a patch by Nick Piggin -- part 1 of 2.
> > >
> > > This patch:
> > >
> > > 1) defines
Yes!... this is a embedded system, and will not have monitor. So, serial
is the default console.
I pass cmdline as "root=/dev/ram rw console=ttyS0,115200"
Thanks
Siva
-Original Message-
From: Scott Russell [mailto:[EMAIL PROTECTED]
Sent: Wednesday, December 19, 2007 3:31 PM
To: Siva
Crispin Cowan <[EMAIL PROTECTED]> wrote:
> > This is used, for example, by CacheFiles which has to transparently access
> > the cache on behalf of a process that thinks it is doing, say, NFS
> > accesses with a potentially inappropriate (with respect to accessing the
> > cache) set of security
Quoting Tetsuo Handa ([EMAIL PROTECTED]):
> A brief description about SYAORAN:
>
> SYAORAN stands for "Simple Yet All-important Object Realizing Abiding
> Nexus". SYAORAN is a filesystem for /dev with Mandatory Access Control.
I apologize if I'm commiting a faux pas by asking this, but any
On Wednesday, 19 of December 2007, David Chinner wrote:
> On Tue, Dec 18, 2007 at 05:36:42PM +, Christoph Hellwig wrote:
> >
> > This was broken by my '[XFS] simplify xfs_create/mknod/symlink prototype',
> > which assigned the re-shuffled ondisk dev_t back to the rdev variable in
> >
On Thursday, 20 of December 2007, Christoph Lameter wrote:
> On Thu, 20 Dec 2007, Rafael J. Wysocki wrote:
>
> > > We could reexport drain_local_pages() again but then I do not understand
> > > why we would only drain the pages of this processor and not of all other
> > > processors as well. It
On Wed, 2007-12-19 at 14:33 -0800, Siva Prasad wrote:
> Thank you very much for your response Clemens.
>
> I tried strace on a regular system. It does not show which tty, etc., as it
> uses the stdout (fd = 1) and write(1, ...) to it.
>
> This is not a student project. I am trying to build my
On Sunday 09 December 2007 09:02:11 pm Mike Houston wrote:
> On Mon, 10 Dec 2007 10:31:27 +0800
> Shaohua Li <[EMAIL PROTECTED]> wrote:
> > This should exist in previous kernel (before we remove acpi
> > motherboard driver) too. Basically it's a broken BIOS. Could below
> > patch work around it?
>
On Tue, 18 Dec 2007 20:44:42 -0600
Trevor Highland <[EMAIL PROTECTED]> wrote:
> Change the type of cipher_code from u16 to u8.
I sure hope that Michael knows what's going on here, because these
changelogs aren't very useful. They tell us *what* the patch does (which
was pretty obvious anyway)
On Thursday 20 December 2007 06:28, Peter Zijlstra wrote:
> On Wed, 2007-12-19 at 11:53 -0500, Lee Schermerhorn wrote:
> > On Wed, 2007-12-19 at 11:31 -0500, Rik van Riel wrote:
> > > On Wed, 19 Dec 2007 10:52:09 -0500
> > >
> > > Lee Schermerhorn <[EMAIL PROTECTED]> wrote:
> > > > I keep these
On 12/19/07, Siva Prasad <[EMAIL PROTECTED]> wrote:
>
> Yes!... this is a embedded system, and will not have monitor. So, serial
> is the default console.
>
> I pass cmdline as "root=/dev/ram rw console=ttyS0,115200"
Adding a CONSOLE=/dev/ttyS0 works for me on both Debian and Redhat;
You also
Serge E. Hallyn wrote:
> Quoting Pavel Emelyanov ([EMAIL PROTECTED]):
>> Oren Laadan wrote:
>>> Serge E. Hallyn wrote:
Quoting Oren Laadan ([EMAIL PROTECTED]):
> I hate to bring this again, but what if the admin in the container
> mounts an external file system (eg. nfs, usb, loop
On Wed, 19 Dec 2007, David Chinner wrote:
> Folks,
>
> I just updated a git tree and started getting errors on a
> "copy_keys" macro warning.
>
> The code I've been working on uses a ->copy_keys() method for
> copying the keys in a btree block from one place to another. I've
> been working on
Greg KH wrote:
On Wed, Dec 19, 2007 at 05:17:46PM -0500, [EMAIL PROTECTED] wrote:
OVERVIEW
===
The patches should be applied in sequence to obviate any
possible build problems.
The patch-set was built against 2.6.24-rc5
Description
===
There exist devices that do not respond
On Tuesday 18 December 2007 10:59:18 am Jean Delvare wrote:
> The real cause is pretty clear here: broken BIOS. In an ideal world we
> would ask the manufacturer for a fixed BIOS and they would give that to
> us, unfortunately my experience is that it won't happen. So, unless we
> accept that idea
| The following patchset cleans up the atmel_serial driver a bit,
| moves a significant portion of the interrupt handler into a tasklet,
| and adds DMA support. This is the result of a combined effort by Chip
| Coldwell, Remy Bohmer and me. The patches should apply cleanly onto
| Linus' latest
Thanks to everyone for your last round of review comments and changes to
the kobject documentation.
I now have over 130 patches reworking the kset/ktype and kobject apis in
the kernel tree, and here is the updated documentation and example code
that shows how things work now.
Things different
/*
* Sample kobject implementation
*
* Copyright (C) 2004-2007 Greg Kroah-Hartman <[EMAIL PROTECTED]>
* Copyright (C) 2007 Novell Inc.
*
* Released under the GPL version 2 only.
*
*/
#include
#include
#include
#include
#include
/*
* This module shows how to create a simple
/*
* Sample kset and ktype implementation
*
* Copyright (C) 2004-2007 Greg Kroah-Hartman <[EMAIL PROTECTED]>
* Copyright (C) 2007 Novell Inc.
*
* Released under the GPL version 2 only.
*
*/
#include
#include
#include
#include
#include
/*
* This module shows how to create a kset in
On Tue, 18 Dec 2007 23:00:52 +0800
"peerchen" <[EMAIL PROTECTED]> wrote:
> According to the HyperTransport spec, 'En' indicate if the MSI Mapping is
> active.
> Set the 'En' bit when setup pci and add the quirk for some nvidia devices.
>
> The patch base on kernel 2.6.24-rc5
>
>
On Dec 20, 2007 12:07 AM, Alan Stern <[EMAIL PROTECTED]> wrote:
>
> On Wed, 19 Dec 2007, Dave Young wrote:
>
> > I tested on another machine with kernel 2.6.24-rc2. And the result is
> > diffrent again.
> > Here is the result:
> >
> > 1. on 2.6.24-rc2, when I plugin the player the kernel reports
On Wed, 19 Dec 2007 16:41:25 -0800
Andrew Morton <[EMAIL PROTECTED]> wrote:
> It would be better to just add a stub implementation of
> ht_enable_msi_mapping() for all the other architectures - avoid fancy cpp
> tricks.
And by this I really do mean going into each include/asm-*/pci.h and adding
On Thursday 20 December 2007 00:20:21 Bjorn Helgaas wrote:
> I suspect the manufacturers would say "Oh, the sensors? The BIOS
> isn't broken, you're just supposed to use WMI or some (undocumented)
> ACPI device to get at those."
It's quite possible - can we have DSDTs for the boards in question
Greg KH wrote:
Please do not respond privately, please respond back on the list so that
everyone can see. That way I will respond, to do otherwise is rude to
the rest of the community...
thanks,
greg k-h
I'm very sorry.
It is certainly not my intention to be rude.
--
To unsubscribe from
> On Sun, 16 Dec 2007, Krzysztof Oledzki wrote:
> >
> > I'll confirm this tomorrow but it seems that even switching to data=ordered
> > (AFAIK default o ext3) is indeed enough to cure this problem.
>
> Ok, do we actually have any ext3 expert following this? I have no idea
> about what the
Hi Ingo,
Here's another round of the pagetable unification patches. I've done a
few dozen rounds of randconfig builds on both 32- and 64-bit, so I hope
that will prevent compile problems in your test environment.
I've also boot-tested 64-bit and 32-bit PAE/non-PAE configs (both paravirt
and
Clean up a number of warnings about printk format mismatches.
Signed-off-by: Jeremy Fitzhardinge <[EMAIL PROTECTED]>
---
arch/x86/kernel/setup_32.c |6 +++---
arch/x86/mm/fault_32.c |2 +-
arch/x86/mm/fault_64.c |8
include/asm-x86/pgtable_64.h |8
Fix up various pieces of unconventional formatting in
asm-x86/pgtable*.h. In some cases, the old formatting was arguablly
clearer with a wide enough terminal, but this patch gives the option
of using a more standard form.
Signed-off-by: Jeremy Fitzhardinge <[EMAIL PROTECTED]>
---
Make pte_t have the same basic structure for all pagetable formats so
that it can be accessed in a uniform way.
This allows a number of follow-on opportunities for sharing code.
Signed-off-by: Jeremy Fitzhardinge <[EMAIL PROTECTED]>
---
arch/x86/kernel/efi_64.c |2
All x86 modes and architectures have very similar pagetable
structures: the page flags, the accessors for testing/setting them,
and the combinations of page flags used for kernel and usermode
mappings are all the same. The main difference is between 32 and
64-bit pagetable entries, with the
On Dec 19, 2007 7:09 PM, Rafael J. Wysocki <[EMAIL PROTECTED]> wrote:
>
> On Thursday, 20 of December 2007, Christoph Lameter wrote:
> > On Thu, 20 Dec 2007, Rafael J. Wysocki wrote:
> >
> > > > We could reexport drain_local_pages() again but then I do not understand
> > > > why we would only
Carlos Corbacho wrote:
On Thursday 20 December 2007 00:20:21 Bjorn Helgaas wrote:
I suspect the manufacturers would say "Oh, the sensors? The BIOS
isn't broken, you're just supposed to use WMI or some (undocumented)
ACPI device to get at those."
It's quite possible - can we have DSDTs for
On Thursday, 20 of December 2007, Miles Lane wrote:
> On Dec 19, 2007 7:09 PM, Rafael J. Wysocki <[EMAIL PROTECTED]> wrote:
>
> > On Thursday, 20 of December 2007, Christoph Lameter wrote:
> > > On Thu, 20 Dec 2007, Rafael J. Wysocki wrote:
> > >
> > > > > We could reexport drain_local_pages()
Unify common definitions in page*.h. To simplify other code, I added
typedefs for the value of pte/pmd/pud/pgd values, so they can be used
symbolically elsewhere without needing to have lots of 32/64/PAE
tests.
Also, add PAGETABLE_LEVELS define so that other definitions can test
for it directly
On Thursday 20 December 2007 12:05, Jan Kara wrote:
> > On Sun, 16 Dec 2007, Krzysztof Oledzki wrote:
> > > I'll confirm this tomorrow but it seems that even switching to
> > > data=ordered (AFAIK default o ext3) is indeed enough to cure this
> > > problem.
> >
> > Ok, do we actually have any ext3
Hi,
This patch series is a major rework of the ide-cd driver.
The motivations behind it are twofold:
* ide-cd is still in use but because it has been out of luck for maintainers
lately the code become quite hard to debug and maintain - this puts it back
into the shape
* aid efforts of
cdi->mask is cleared by ide_cdrom_register() which is called after the quirk.
Fix it by adding new ->no_speed_select flag to struct ide_cd_config_flags
and using it in ide_cdrom_register() to set CDC_SELECT_SPEED flag.
Signed-off-by: Bartlomiej Zolnierkiewicz <[EMAIL PROTECTED]>
---
* Fix ACER/AOpen 24X CDROM speed reporting on big-endian machines
by adding missing le16_to_cpu() calls.
While at it:
* Replace ntohs() by be16_to_cpu().
Signed-off-by: Bartlomiej Zolnierkiewicz <[EMAIL PROTECTED]>
---
drivers/ide/ide-cd.c |8
1 file changed, 4 insertions(+), 4
> Why does link(2) not support hard-linking across bind mount points
> of the same underlying filesystem ?
Whenever we get mount -r --bind working properly (which I use to place
copies of necessary shared libraries inside chroot jails while allowing
page cache sharing), this feature would break
Signed-off-by: Bartlomiej Zolnierkiewicz <[EMAIL PROTECTED]>
---
drivers/ide/ide-cd.c |5 -
1 file changed, 4 insertions(+), 1 deletion(-)
Index: b/drivers/ide/ide-cd.c
===
--- a/drivers/ide/ide-cd.c
+++
Signed-off-by: Bartlomiej Zolnierkiewicz <[EMAIL PROTECTED]>
---
drivers/ide/ide-cd.c | 13 -
1 file changed, 8 insertions(+), 5 deletions(-)
Index: b/drivers/ide/ide-cd.c
===
--- a/drivers/ide/ide-cd.c
+++
Signed-off-by: Bartlomiej Zolnierkiewicz <[EMAIL PROTECTED]>
---
drivers/ide/ide-cd.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
Index: b/drivers/ide/ide-cd.c
===
--- a/drivers/ide/ide-cd.c
+++ b/drivers/ide/ide-cd.c
Unify writing and reading handling in cdrom_pc_intr() using xfer_func_t.
There should be no functionality changes caused by this patch.
Signed-off-by: Bartlomiej Zolnierkiewicz <[EMAIL PROTECTED]>
---
drivers/ide/ide-cd.c | 47 +--
1 file changed,
Add ide_cd_pad_transfer() helper and use it in cdrom_[new]pc_intr()
and cdrom_{read,write}_check_ireason().
There should be no functionality changes caused by this patch.
Signed-off-by: Bartlomiej Zolnierkiewicz <[EMAIL PROTECTED]>
---
-39 bytes
drivers/ide/ide-cd.c | 51
Signed-off-by: Bartlomiej Zolnierkiewicz <[EMAIL PROTECTED]>
---
drivers/ide/ide-cd.c | 23 +++
1 file changed, 11 insertions(+), 12 deletions(-)
Index: b/drivers/ide/ide-cd.c
===
--- a/drivers/ide/ide-cd.c
Signed-off-by: Bartlomiej Zolnierkiewicz <[EMAIL PROTECTED]>
---
drivers/ide/ide-cd.h | 10 --
1 file changed, 10 deletions(-)
Index: b/drivers/ide/ide-cd.h
===
--- a/drivers/ide/ide-cd.h
+++ b/drivers/ide/ide-cd.h
@@
1 - 100 of 761 matches
Mail list logo
