* Glauber de Oliveira Costa <[EMAIL PROTECTED]> wrote:
> Since the last version of it received no comments on the interfaces,
> here it goes a version, that I feel ready for inclusion.
>
> The comments regarding style, specially the elimination of the
> #defines in the desc_struct definition
Rene Herman wrote:
> Good day.
>
> Would some people on x86 (both 32 and 64) be kind enough to compile
> and run the attached program? This is about testing how long I/O port
> access to port 0x80 takes. It measures in CPU cycles so CPU speed is
> crucial in reporting.
>
> Posted a previous
On Wed, Dec 12, 2007 at 11:00:46AM -0500, [EMAIL PROTECTED] wrote:
> Mauro Carvalho Chehab wrote:
>...
> What we really need is to make the Kconfig selection behave as if it
> depends on VIDEO_TUNER, but only if VIDEO_TUNER is selected. I know
> that sounds redundant, but that would actually
Ilpo Järvinen wrote:
> On Wed, 5 Dec 2007, David Miller wrote:
>
>> From: Reuben Farrelly <[EMAIL PROTECTED]>
>> Date: Thu, 06 Dec 2007 17:59:37 +1100
>>
>>> On 5/12/2007 4:17 PM, Andrew Morton wrote:
- Lots of device IDs have been removed from the e1000 driver and moved over
to
elv_register() always returns 0, and there isn't anything it does where
it should return an error (the only error condition is so grave that
it's handled with a BUG_ON).
Signed-off-by: Adrian Bunk <[EMAIL PROTECTED]>
---
block/as-iosched.c |4 +++-
block/cfq-iosched.c |8
On Wed, Dec 12, 2007 at 08:46:18AM -0800, Daniel Phillips wrote:
> Incidentally, we ran our tests with 128 knfsd threads. The default of 8
> threads produces miserable performance on the SSD, which gave us a good
> scare on our initial test run. It would be very nice to implement an
>
From: Andrew Gallatin <[EMAIL PROTECTED]>
Date: Wed, 12 Dec 2007 12:29:23 -0500
> Is the netif_running() check even required?
No, it is not.
When a device is brought down, one of the first things
that happens is that we wait for all pending NAPI polls
to complete, then block any new polls from
Not to long ago preempt_max_latency was microseconds, and someplace
along the way it turned into cycles. That's a bit unintuitive, so I
converted it back to microseconds.
Signed-Off-By: Daniel Walker <[EMAIL PROTECTED]>
---
include/linux/clocksource.h | 12 ++--
Hi Mike,
On Wed, 12 Dec 2007 15:25:10 +, "Miller, Mike (OS Dev)" <[EMAIL PROTECTED]>
wrote:
> > Index: 2.6.24-rc4/drivers/block/cciss.c
> > ===
> > --- 2.6.24-rc4.orig/drivers/block/cciss.c
> > +++
[I apologize for loosing threading, I'm replying from the archives]
> The problem is that the driver is doing a NAPI completion and
> re-enabling chip interrupts with work_done == weight, and that is
> illegal.
The only time at least myri10ge will do this is due to
the !netif_running(netdev)
Fix my original mistake of using CONFIG_CRITICAL_TIMING , which only
covers preempt and irqs-off timing.. Convert to CONFIG_LATENCY_TIMING,
so wakeup timing also has these.
Signed-Off-By: Daniel Walker <[EMAIL PROTECTED]>
---
kernel/sysctl.c |2 +-
1 file changed, 1 insertion(+), 1
On Wed, Dec 12, 2007 at 04:11:19PM +0800, Huang, Ying wrote:
> On Tue, 2007-12-11 at 23:35 -0800, Greg KH wrote:
> > > +static struct attribute *boot_params_attrs[] = {
> > > + _params_version_attr.attr,
> > > + NULL
> > > +};
> > > +
> > > +static struct attribute_group boot_params_attr_group = {
David Miller wrote:
From: Andrew Gallatin <[EMAIL PROTECTED]>
Date: Wed, 12 Dec 2007 12:29:23 -0500
Is the netif_running() check even required?
No, it is not.
When a device is brought down, one of the first things
that happens is that we wait for all pending NAPI polls
to complete, then
On Wed, Dec 12, 2007 at 04:59:51PM +0800, Huang, Ying wrote:
> This patch export the boot parameters via sysfs. This can be used for
> debugging and kexec.
>
> The files added are as follow:
>
> /sys/kernel/boot_params/data : binary file for struct boot_params
> /sys/kernel/boot_params/version
On Wed, Dec 12 2007, Adrian Bunk wrote:
> elv_register() always returns 0, and there isn't anything it does where
> it should return an error (the only error condition is so grave that
> it's handled with a BUG_ON).
Principally it could return -EEXIST for the BUG_ON(), but there's little
point.
On Wednesday 12 December 2007 09:46, J. Bruce Fields wrote:
> On Wed, Dec 12, 2007 at 08:46:18AM -0800, Daniel Phillips wrote:
> > Incidentally, we ran our tests with 128 knfsd threads. The default
> > of 8 threads produces miserable performance on the SSD, which gave
> > us a good scare on our
* Glauber de Oliveira Costa <[EMAIL PROTECTED]> wrote:
> diff --git a/include/asm-x86/ldt.h b/include/asm-x86/ldt.h
> index 20c5972..49013fd 100644
> --- a/include/asm-x86/ldt.h
> +++ b/include/asm-x86/ldt.h
> @@ -5,6 +5,7 @@
> */
> #ifndef _ASM_X86_LDT_H
> #define _ASM_X86_LDT_H
> +#include
Ingo Molnar wrote:
* Ingo Molnar <[EMAIL PROTECTED]> wrote:
Ingo, in the absense of further complaints, could you please push
to the x86 tree?
yeah, i've added them.
the patches cause a spontaneous reboot on x86 64-bit, around the time
when bootup hits user-space. It's due to one of the 25
Casey Schaufler <[EMAIL PROTECTED]> wrote:
> You may need to have an application, say cachefileselinuxcontext, that will
> read the current policy and spit out an appropriate value of "",
> but that can be separate and LSM specific without mucking up your basic
> infrastructure applications.
Greetings,
Dmitry, any chance of getting this into the RC since its really a bugfix?
Anyhow, compiled cleanly with patch applied.
shortlog:
* This patch fixes the HP Jornada 6xx keyboard default keymap which had some
bad keymap values. This resulted in wrong
key being returned when pressed
* Ingo Molnar <[EMAIL PROTECTED]> wrote:
> > > Ingo, in the absense of further complaints, could you please push
> > > to the x86 tree?
> >
> > yeah, i've added them.
>
> the patches cause a spontaneous reboot on x86 64-bit, around the time
> when bootup hits user-space. It's due to one of
* Ingo Molnar <[EMAIL PROTECTED]> wrote:
> > Since the last version of it received no comments on the interfaces,
> > here it goes a version, that I feel ready for inclusion.
> >
> > The comments regarding style, specially the elimination of the
> > #defines in the desc_struct definition were
Greg KH wrote:
On Wed, Dec 12, 2007 at 04:59:51PM +0800, Huang, Ying wrote:
This patch export the boot parameters via sysfs. This can be used for
debugging and kexec.
The files added are as follow:
/sys/kernel/boot_params/data: binary file for struct boot_params
On Wed, Dec 12 2007 at 19:06 +0200, Kiyoshi Ueda <[EMAIL PROTECTED]> wrote:
> Hi,
>
> On Wed, 12 Dec 2007 11:09:12 +0200, Boaz Harrosh <[EMAIL PROTECTED]> wrote:
>>> Index: 2.6.24-rc4/drivers/block/xsysace.c
>>> ===
>>> ---
On Wed, Dec 12, 2007 at 11:40:13AM -0500, Dave Jones wrote:
> > powernow-k8: Found 1 AMD Athlon(tm) 64 X2 Dual Core Processor 3800+
> processors (1 cpu cores) (version 2.20.00)
> > powernow-k8: BIOS error - no PSB or ACPI _PSS objects
> > [ cut here ]
> > kernel
On Wed, 2007-12-12 at 17:08 +0100, Marcel Holtmann wrote:
> Hi Oliver,
>
> > > I noticed that on my macbook pro1,1 the bluetooth device is gone after
> > > suspend to ram, i.e.
> >
> > Is this a regression?
> > Does it work if you unload hci_usb before you suspend?
> > If so, please recompile
Eric Dumazet wrote:
Chris Friesen a écrit :
Is this expected behaviour?
Probably not... Still a 2.6.14 kernel ?
Yep. Embedded hardware, so I'm unable to test with a more recent kernel.
Could you send the result of :
strace ip neigh show
I've attached two strace runs, one of "ip neigh
On 12/11/07, Rene Herman <[EMAIL PROTECTED]> wrote:
> Good day.
>
> Would some people on x86 (both 32 and 64) be kind enough to compile and run
> the attached program? This is about testing how long I/O port access to port
> 0x80 takes. It measures in CPU cycles so CPU speed is crucial in
David Miller wrote:
> From: Andrew Gallatin <[EMAIL PROTECTED]>
> Date: Wed, 12 Dec 2007 12:29:23 -0500
>
>> Is the netif_running() check even required?
>
> No, it is not.
>
> When a device is brought down, one of the first things
> that happens is that we wait for all pending NAPI polls
> to
Jiri Slaby wrote:
On Dec 12, 2007 9:48 AM, Jiri Slaby <[EMAIL PROTECTED]> wrote:
On 12/12/2007 12:31 AM, Rene Herman wrote:
Good day.
Would some people on x86 (both 32 and 64) be kind enough to compile and
run the attached program? This is about testing how long I/O port access
model name
just asking, given that:
include/asm-x86/page_64.h:#define THREAD_SIZE (PAGE_SIZE << THREAD_ORDER)
include/asm-arm/page-nommu.h:#define KTHREAD_SIZE (8192)
include/asm-arm/page-nommu.h:#define KTHREAD_SIZE PAGE_SIZE
include/asm-cris/processor.h:#define THREAD_SIZE PAGE_SIZE
On Wed, Dec 12, 2007 at 07:22:07PM +0100, Kristoffer Ericson wrote:
> shortlog:
> * This patch fixes the HP Jornada 6xx keyboard default keymap which had some
> bad keymap values. This resulted in wrong
> key being returned when pressed (example : key y returned 'r').
> * Also, while we are at it
> -Message d'origine-
> De : [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] De la part de Dhaval Giani
>
> On Wed, Dec 12, 2007 at 07:57:33AM -0500, Fortier,Vincent
> [Montreal] wrote:
> > > -Message d'origine-
> > > De : Dhaval Giani [mailto:[EMAIL PROTECTED]
> > >
> > > On
From: Harvey Harrison <[EMAIL PROTECTED]>
Date: Wed, 12 Dec 2007 00:09:03 -0800
> X86_32 was the last user of the FASTCALL macro, now that it
> uses regparm(3) by default, this macro expands to nothing.
>
> Signed-off-by: Harvey Harrison <[EMAIL PROTECTED]>
Applied to net-2.6.25, thanks.
--
To
Stephen Smalley <[EMAIL PROTECTED]> wrote:
> That sounds workable, although I think he will want a more specific hook
> than security_secctx_to_secid(), or possibly a second hook call, that
> would not only validate the context but authorize the use of it by the
> cachefilesd process. And then
Casey Schaufler <[EMAIL PROTECTED]> wrote:
> What sort of authorization are you thinking of? I would expect
> that to have been done by cachefileselinuxcontext (or
> cachefilesspiffylsmcontext) up in userspace. If you're going to
> rely on userspace applications for policy enforcement they need
>
* Glauber de Oliveira Costa <[EMAIL PROTECTED]> wrote:
> Ingo Molnar wrote:
>> * Ingo Molnar <[EMAIL PROTECTED]> wrote:
>>
> Ingo, in the absense of further complaints, could you please push to
> the x86 tree?
yeah, i've added them.
>>> the patches cause a spontaneous reboot on x86
before i pulled the patches i narrowed the problem down to one of the
last ~6 patches in your 25-patch series. I couldnt continue bisecting it
when i saw that process_64.c warning.
Ingo
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message
On Wed, 2007-12-12 at 08:51 -0800, Casey Schaufler wrote:
> --- Stephen Smalley <[EMAIL PROTECTED]> wrote:
>
> > On Tue, 2007-12-11 at 15:04 -0800, Casey Schaufler wrote:
> > > --- David Howells <[EMAIL PROTECTED]> wrote:
> > >
> > > > Stephen Smalley <[EMAIL PROTECTED]> wrote:
> > > >
> > > >
Remove the bogus netif_running() check from myri10ge_poll().
This eliminates any chance that myri10ge_poll() can trigger
an oops by calling netif_rx_complete() and returning
with work_done == budget.
Signed-off-by: Andrew Gallatin <[EMAIL PROTECTED]>
diff --git a/drivers/net/myri10ge/myri10ge.c
On Mit, 2007-12-12 at 10:02 -0800, Daniel Phillips wrote:
> On Wednesday 12 December 2007 09:46, J. Bruce Fields wrote:
[...]
> > People have proposed writing a daemon that just reads
> > /proc/net/rpc/nfsd periodically and uses that to adjust the number of
> > threads from userspace, probably
On Wed, Dec 12, 2007 at 12:46:21PM -0200, Mauro Carvalho Chehab wrote:
> Em Qua, 2007-12-12 às 08:42 -0500, Michael Krufky escreveu:
> > > ERROR: "tea5761_attach" [drivers/media/video/tuner.ko] undefined!
> > > ERROR: "tea5761_autodetection" [drivers/media/video/tuner.ko] undefined!
> > > ERROR:
Chris Friesen a écrit :
Eric Dumazet wrote:
Chris Friesen a écrit :
Is this expected behaviour?
Probably not... Still a 2.6.14 kernel ?
Yep. Embedded hardware, so I'm unable to test with a more recent kernel.
And what is the version of "ip" command you have on this machine ?
ip -V
I have been having a fun time testing this on my AMD64x2 system.
Since out's to port 80 hang the system hard after a while, I can run a
test just after booting, but the next run will typically hang it.
I did also test two ports thought to be unused. They do *not* hang the
system. Thus
On Thu, 13 Dec 2007 03:45:58 +0900
Paul Mundt <[EMAIL PROTECTED]> wrote:
> On Wed, Dec 12, 2007 at 07:22:07PM +0100, Kristoffer Ericson wrote:
> > shortlog:
> > * This patch fixes the HP Jornada 6xx keyboard default keymap which had
> > some bad keymap values. This resulted in wrong
> > key
On Dec 12, 2007 11:37 AM, Shane <[EMAIL PROTECTED]> wrote:
> On Dec 12, 2007 9:21 AM, Mauro Carvalho Chehab <[EMAIL PROTECTED]> wrote:
> ...
> > The proper solution is provided by this changeset:
> >
Linus, please pull from
git://git.kernel.org/pub/scm/linux/kernel/git/drzeus/mmc.git for-linus
to receive the following updates:
drivers/mmc/host/sdhci.c | 63 ++---
drivers/mmc/host/sdhci.h |3 +-
include/linux/mmc/host.h |4 ---
> >
> > Why is this removed?
>
> Sorry for the less explanation.
>
> Because it is done in __end_that_request_first() called from
> blk_end_request().
> I'll add the explanation to the patch description when I
> update the patch.
>
Thank you. I've Acked the patch.
-- mikem
--
To unsubscribe from
> What is the fix you suggest, to add a device query that tells you for
> which verbs the documentation does not apply? or enhance the code of the
> map_phys_fmr verb within the ehca driver to return error if called
> from non-sleepable context?
I think the right fix for iSER would be to
On 12-12-07 19:39, SL Baur wrote:
model name : Intel(R) Pentium(R) 4 CPU 3.20GHz
cpu MHz : 3201.345
cycles: out 3026, in 2204
cycles: out 3031, in 2182
cycles: out 3019, in 2196
cycles: out 3030, in 2201
cycles: out 3013, in 2186
Thank you. I just posted the combined results,
Greg KH wrote:
This is a binary structure defined by protocol;
What protocol? Is this a "standard" documented somewhere?
Yes, see Documentation/i386/* (although some of it is documented by
reference to include/asm-x86/boot_params.h).
in that way it's not significantly different from
Ingo Molnar wrote:
* Glauber de Oliveira Costa <[EMAIL PROTECTED]> wrote:
Ingo Molnar wrote:
* Ingo Molnar <[EMAIL PROTECTED]> wrote:
Ingo, in the absense of further complaints, could you please push to
the x86 tree?
yeah, i've added them.
the patches cause a spontaneous reboot on x86
From: Andrew Gallatin <[EMAIL PROTECTED]>
Date: Wed, 12 Dec 2007 13:38:34 -0500
> Remove the bogus netif_running() check from myri10ge_poll().
>
> This eliminates any chance that myri10ge_poll() can trigger
> an oops by calling netif_rx_complete() and returning
> with work_done == budget.
>
>
On Wed, Dec 12, 2007 at 09:54:12AM -0800, H. Peter Anvin wrote:
> Greg KH wrote:
>> On Wed, Dec 12, 2007 at 04:59:51PM +0800, Huang, Ying wrote:
>>> This patch export the boot parameters via sysfs. This can be used for
>>> debugging and kexec.
>>>
>>> The files added are as follow:
>>>
>>>
Jeremy Fitzhardinge wrote:
Bodo Eggert wrote:
Not BUG_ON(memcmp(xen_start_info->magic, "xen-3.", 6) != 0); ?
I don't thin Xen version 32 will be compatible ...
It had better be; if it loads the kernel, it should present a xen-3
compatible ABI.
If xen-32.0 should be compatible than
I'm looking at unifying the various pgalloc+pgd_lists mechanisms between
32-bit (PAE and non-PAE) and 64-bit, so I'm trying to understand why
these differences exist in the first place.
Change da8f153e51290e7438ba7da66234a864e5d3e1c1 reverted the use of
quicklists for allocating pagetables,
On Wed, Dec 12, 2007 at 09:45:07AM -0800, Greg Kroah-Hartman wrote:
> Well, I respectively disagree. sysfs is NOT for exporting various
> binary kernel structures to userspace directly. Again, the binary files
> in sysfs are for chunks of memory that are PASS-THROUGH from hardware to
>
Hi everyone.
That was a succesful request, thanks to all who responded. This message also
just now went out with all the respondents in CC but I believe that copy
isn't making the list, so here's one without...
In total you provided 60 reports which are listed below in increasing order
of
On Wed, 12 Dec 2007 14:43:42 +0100 Anders Henke <[EMAIL PROTECTED]> wrote:
> Am 12.12.2007 schrieb Miquel van Smoorenburg:
> > On Wed, 2007-12-12 at 03:38 -0800, Andrew Morton wrote:
> > > On Wed, 12 Dec 2007 11:58:41 +0100 Anders Henke <[EMAIL PROTECTED]> wrote:
> > >
> > > > Hi,
> > > >
> > >
[Added CC to [EMAIL PROTECTED]
On Wednesday, 12 of December 2007, Mitch wrote:
> Can anyone help with this ? This seems to be a true SMP bug - the same
> kernel on another UP machine is working fine (although different h/w).
> Seems like stress (find for example) can easily trigger this. Does
--- David Howells <[EMAIL PROTECTED]> wrote:
> Casey Schaufler <[EMAIL PROTECTED]> wrote:
>
> > You may need to have an application, say cachefileselinuxcontext, that will
> > read the current policy and spit out an appropriate value of "",
> > but that can be separate and LSM specific without
On 12-12-07 19:44, H. Peter Anvin wrote:
model name : Intel(R) Xeon(R) CPU E5335 @ 2.00GHz
cycles: out 3217, in 1898
1.6 µs, on the high end
model name : Dual Core AMD Opteron(tm) Processor 275
cycles: out 5508, in 5524
Definitely an outlier; 2.5 µs here.
Jah, I
Ilpo Järvinen wrote:
> On Wed, 5 Dec 2007, Andrew Morton wrote:
>
>> On Thu, 06 Dec 2007 17:59:37 +1100 Reuben Farrelly <[EMAIL PROTECTED]> wrote:
>>
>>> This non fatal oops which I have just noticed may be related to this change
>>> then
>>> - certainly looks networking related.
>> yep, but it
From: Andrew Morton <[EMAIL PROTECTED]>
Date: Tue, 11 Dec 2007 16:57:00 -0800
> On Sun, 9 Dec 2007 22:34:33 +0100
> Marcin __lusarz <[EMAIL PROTECTED]> wrote:
>
> > fbcon: fix sparse warning about shadowing 'p' symbol
> >
>
> Please always quote error messages and warnings in the changelog
The CAPACITY_LEVEL stuff defines various levels of charge; however, what
is the difference between them? What differentiates between HIGH and NORMAL,
LOW and CRITICAL, etc?
As it appears that these are fairly arbitrary, we end up making such policy
decisions in the kernel (or in hardware).
In power_supply_create_attrs(), we create static attributes as referenced
by power_supply_static_attrs[i]. After that, if we fail, we unregister
via power_supply_static_attrs[psy->properties[i]]. This is incorrect, as
psy->properties has absolutely no bearing on static attribs. This patch
From: Andrew Morton <[EMAIL PROTECTED]>
Date: Tue, 11 Dec 2007 16:44:45 -0800
> So I'd propose this:
I've applied this to net-2.6, thanks Andrew.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at
Ai aici informatii gratuite despre o afacere care a revolutiuonat internetul.
Nu mai astepta si da click caci nu te costa nimic.
clik aici
www.uvmeguru.com/ro/1?r=412390
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Some kprobe structure members had a superfluous e in their
name.
eflags -> flags
esp -> sp
Signed-off-by: Harvey Harrison <[EMAIL PROTECTED]>
---
Ingo, this applies on top of my kprobes unification patch.
arch/x86/kernel/kprobes_32.c | 34 +-
Kyle McMartin wrote:
On Wed, Dec 12, 2007 at 12:31:18AM +0100, Rene Herman wrote:
asm volatile ("rdtsc": "=A" (tsc));
rdtsc returns a 64-bit value in two 32-bit regs, you need to do
inline unsigned long long rdtsc(void)
{
unsigned int lo, hi;
asm volatile ("rdtsc":
Casey Schaufler <[EMAIL PROTECTED]> wrote:
> Put the result into /etc/cachefiles.conf.
Ewww. Runtime mangling of the configuration. I suppose it doesn't have to be
in that file with the rest of the config.
David
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the
> "=A" works on 32-bit systems (only), obviously, and gcc will generally
> produce slightly better code as a result (gcc could really use a
> register renaming/copy propagation step *after* multi-register entities
I believe gcc 4.3 (or maybe 4.2) does that already -- it splits them much
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
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
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.
Also converts some (but not all) function-like macros into inline
> -Original Message-
> From: Kiyoshi Ueda [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, December 11, 2007 4:50 PM
> To: [EMAIL PROTECTED]
> Cc: linux-kernel@vger.kernel.org; [EMAIL PROTECTED];
> [EMAIL PROTECTED]; [EMAIL PROTECTED];
> [EMAIL PROTECTED]; [EMAIL PROTECTED]; Miller, Mike (OS
--- David Howells <[EMAIL PROTECTED]> wrote:
> Casey Schaufler <[EMAIL PROTECTED]> wrote:
>
> > What sort of authorization are you thinking of? I would expect
> > that to have been done by cachefileselinuxcontext (or
> > cachefilesspiffylsmcontext) up in userspace. If you're going to
> > rely
Andi Kleen wrote:
"=A" works on 32-bit systems (only), obviously, and gcc will generally
produce slightly better code as a result (gcc could really use a
register renaming/copy propagation step *after* multi-register entities
I believe gcc 4.3 (or maybe 4.2) does that already -- it splits
On Tue, Dec 11, 2007 at 09:50:32PM -0500, Dave Jones wrote:
> On Tue, Dec 11, 2007 at 04:57:00PM -0800, Andrew Morton wrote:
>
> > > --- a/drivers/video/console/fbcon.c
> > > +++ b/drivers/video/console/fbcon.c
> > > @@ -2795,7 +2795,7 @@ static int fbcon_scrolldelta(struct vc_data *vc,
> int
On Wed, 2007-12-12 at 18:29 +, David Howells wrote:
> Stephen Smalley <[EMAIL PROTECTED]> wrote:
>
> > That sounds workable, although I think he will want a more specific hook
> > than security_secctx_to_secid(), or possibly a second hook call, that
> > would not only validate the context but
On Wed, 2007-12-12 at 11:16 -0800, Andrew Morton wrote:
> On Wed, 12 Dec 2007 14:43:42 +0100 Anders Henke <[EMAIL PROTECTED]> wrote:
>
> > Am 12.12.2007 schrieb Miquel van Smoorenburg:
> > > On Wed, 2007-12-12 at 03:38 -0800, Andrew Morton wrote:
> > > > On Wed, 12 Dec 2007 11:58:41 +0100 Anders
Sadly, I've been busy with other crises in my day job for the last few
days. I did modify Rene's test program and ran it on my "problem"
machine, with the results below.
The interesting part of this is that port 80 seems to respond to "in"
instructions faster than the presumably "unused"
With the x86 removal, FASTCALL is always empty now.
Signed-off-by: Harvey Harrison <[EMAIL PROTECTED]>
---
arch/um/kernel/ksyms.c |4 ++--
include/asm-um/linkage.h |1 -
2 files changed, 2 insertions(+), 3 deletions(-)
diff --git a/arch/um/kernel/ksyms.c b/arch/um/kernel/ksyms.c
index
FASTCALL() is always empty.
Signed-off-by: Harvey Harrison <[EMAIL PROTECTED]>
---
arch/x86/kernel/acpi/sleep_32.c |2 +-
arch/x86/kernel/vm86_32.c |2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/arch/x86/kernel/acpi/sleep_32.c
--- Stephen Smalley <[EMAIL PROTECTED]> wrote:
> On Wed, 2007-12-12 at 11:44 -0800, Casey Schaufler wrote:
> > --- David Howells <[EMAIL PROTECTED]> wrote:
> >
> > > Casey Schaufler <[EMAIL PROTECTED]> wrote:
> > >
> > > > What sort of authorization are you thinking of? I would expect
> > > >
FASTCALL is always empty after the x86 removal.
Signed-off-by: Harvey Harrison <[EMAIL PROTECTED]>
---
fs/aio.c |2 +-
include/asm-m32r/signal.h |2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/fs/aio.c b/fs/aio.c
index 9dec7d2..8a37dbb 100644
---
Note, that should have been [PATCH RT], this is NOT for mainline!
-- Steve
--
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 Wed, Dec 12, 2007 at 02:40:09PM -0500, Steven Rostedt wrote:
>
> In commit 76d2160147f43f982dfe881404cfde9fd0a9da21 lazy irq disabling
> was implemented, and the simple irq handler had a masking set to it.
>
> Remy Bohmer discovered that some devices in the ARM architecture
> would trigger
On Wed, Dec 12, 2007 at 02:12:56PM -0500, Andres Salomon wrote:
>
> The CAPACITY_LEVEL stuff defines various levels of charge; however, what
> is the difference between them? What differentiates between HIGH and NORMAL,
> LOW and CRITICAL, etc?
>
> As it appears that these are fairly arbitrary,
On Wed, Dec 12, 2007 at 02:12:59PM -0500, Andres Salomon wrote:
>
> In power_supply_create_attrs(), we create static attributes as referenced
> by power_supply_static_attrs[i]. After that, if we fail, we unregister
> via power_supply_static_attrs[psy->properties[i]]. This is incorrect, as
>
On Wed, 2007-12-12 at 11:44 -0800, Casey Schaufler wrote:
> --- David Howells <[EMAIL PROTECTED]> wrote:
>
> > Casey Schaufler <[EMAIL PROTECTED]> wrote:
> >
> > > What sort of authorization are you thinking of? I would expect
> > > that to have been done by cachefileselinuxcontext (or
> > >
With the IO-APIC pcix hack (level=>edge masking), we can receive
interrupts while masked. But these interrupts might be missed.
Also, normal "simple" interrupts might be missed too on leaving of
thread handler.
Signed-off-by: Steven Rostedt <[EMAIL PROTECTED]>
Index:
Andi Kleen <[EMAIL PROTECTED]> writes:
>
> It could enable the extended APIC IDs but not use them?
In which case complaining is still correct (the BIOS was out of sync),
enabling bit 17 is still correct and we are just in overkill mode.
> Anyways I haven't got docs on that NV bridge so I might
Anthony Liguori wrote:
> If xen-32.0 should be compatible than wouldn't xen-24.0 be compatible
> too? I think the point was that you should either be checking for
> 'xen-3.x' or something more general that would accept anything >=
> xen-3.0.
The signature is supposed to be an ABI signature, so
On Wed, 2007-12-12 at 11:20 -0800, Casey Schaufler wrote:
> --- David Howells <[EMAIL PROTECTED]> wrote:
>
> > Casey Schaufler <[EMAIL PROTECTED]> wrote:
> >
> > > You may need to have an application, say cachefileselinuxcontext, that
> > > will
> > > read the current policy and spit out an
--- David Howells <[EMAIL PROTECTED]> wrote:
> Stephen Smalley <[EMAIL PROTECTED]> wrote:
>
> > That sounds workable, although I think he will want a more specific hook
> > than security_secctx_to_secid(), or possibly a second hook call, that
> > would not only validate the context but
Who has attitude problems here? I have indeed learned a lot about assholes.
linux-os (Dick Johnson) wrote:
Yep. We are all wrong. You come out of nowhere and claim to
be right. Goodbye.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
In commit 76d2160147f43f982dfe881404cfde9fd0a9da21 lazy irq disabling
was implemented, and the simple irq handler had a masking set to it.
Remy Bohmer discovered that some devices in the ARM architecture
would trigger the mask, but never unmask it. His patch to do the
unmasking was questioned by
On Wed, Dec 12, 2007 at 01:57:27PM -0500, Shane wrote:
> On Dec 12, 2007 11:37 AM, Shane <[EMAIL PROTECTED]> wrote:
> > On Dec 12, 2007 9:21 AM, Mauro Carvalho Chehab <[EMAIL PROTECTED]> wrote:
> > ...
> > > The proper solution is provided by this changeset:
> > >
[This patch *is* for mainline Linux]
In commit 76d2160147f43f982dfe881404cfde9fd0a9da21 lazy irq disabling
was implemented, and the simple irq handler had a masking set to it.
Remy Bohmer discovered that some devices in the ARM architecture
would trigger the mask, but never unmask it. His patch
801 - 900 of 1182 matches
Mail list logo
