On Wed, 2006-12-13 at 15:46 -0800, Stephen Hemminger wrote:
Split off NAPI part from network device, this patch is build tested
only! It breaks kernel API for network devices, and only three examples
are fixed (skge, sky2, and tg3).
1. Decomposition allows different NAPI - network device
Hello Uli,
Yes, apologies, I had been waiting for an abandoned bugzilla entry
to get attention, and when I realized it was assigned to a dead-end, I
had simply posted the patch without checking for prior messages.
I was further confused by the fact that it hadn't made its way into
any of the
Michael,
I sent a patch to this list on Sunday, that patched the problem. It
seems to be migrated into the wireless-2.6 git tree.
Regards,
Uli
Am 13.12.2006 um 19:17 schrieb Michael Bommarito:
This didn't get much attention on bugzilla and I figured it was
important enough to forward
Michael Bommarito wrote:
Hello Uli,
Yes, apologies, I had been waiting for an abandoned bugzilla entry
to get attention, and when I realized it was assigned to a dead-end, I
had simply posted the patch without checking for prior messages.
I was further confused by the fact that it hadn't made
Nikolai Joukov wrote:
We have designed a new stackable file system that we called RAIF:
Redundant Array of Independent Filesystems.
Great!
We have performed some benchmarking on a 3GHz PC with 2GB of RAM and U320
SCSI disks. Compared to the Linux RAID driver, RAIF has overheads of
On Friday 15 December 2006 10:01, Nikolai Joukov wrote:
Nikolai Joukov wrote:
We have designed a new stackable file system that we called RAIF:
Redundant Array of Independent Filesystems.
Great!
Yes, definitely...
I see the major benefit being in the mobile, industrial and embedded
Nikolai Joukov wrote:
http://www.fsl.cs.sunysb.edu/docs/joukov-phdthesis/thesis.pdf
Figures 9.7 and 9.8 also show profiles of the Linux RAID5 and RAIF5
operation under the same Postmark workload.
Nikolai.
-
Nikolai Joukov, Ph.D.
Filesystems and Storage Laboratory
Stony
We started the project in April 2004. Right now I am using it as my
/home/kolya file system at home. We believe that at this stage RAIF is
mature enough for others to try it out. The code is available at:
ftp://ftp.fsl.cs.sunysb.edu/pub/raif/
The code requires no kernel
Well, Congratulations, Doctor!! [Must be nice to be exiled to Stony
Brook!! Oh, well, not I]
Long Island is a very nice place with lots of vineries and perfect sand
beaches - don't envy :-)
Here's hoping that source exists, and that it is available for us.
I guess, you are subscribed to
Andrew Morton wrote on Thursday, December 14, 2006 5:20 PM
it's hard to disagree.
Begin forwarded message:
On Wed, 2006-12-13 at 08:25 +0100, xb wrote:
Hi all,
Running some IO stress tests on a 8*ways IA64 platform, we got:
BUG: warning at
Hello LKML,
I am observing processes entering uninterruptible sleep apparently due
to an unrelated application using mmap over nfs. Applications in
uninterruptible sleep hang indefinitely while other applications
continue working properly.
The code causing the mmap nfs hangs does the following:
On Thursday 14 December 2006 12:48, Stefan Richter wrote:
[...]
(Anyway, that's unrelated to Gene's issues.)
And which I haven't had a chance to check yet, the camera is still in the
truck and I've been busier than a one legged man in an ass kicking
contest today. I did get 2.6.20-rc1 built
fix vm_events_fold_cpu() build breakage
2.6.20-rc1 does not build properly if CONFIG_VM_EVENT_COUNTERS is set
and CONFIG_HOTPLUG is unset:
CC init/version.o
LD init/built-in.o
LD .tmp_vmlinux1
mm/built-in.o: In function `page_alloc_cpu_notify':
page_alloc.c:(.text+0x56eb):
Ingo,
I've hit this. I compiled the kernel as CONFIG_PREEMPT, and turned off
IRQ's as threads.
BUG: scheduling while atomic: swapper/0x0001/1, CPU#3
Call Trace:
[8026f9b0] dump_trace+0xaa/0x404
[8026fd46] show_trace+0x3c/0x52
[8026fd71] dump_stack+0x15/0x17
On Thu, Dec 14, 2006 at 06:21:49PM +0900, Shinichiro HIDA wrote:
Hi,
;; Sorry for late, and Thanks for following up.
In [EMAIL PROTECTED]
David Chinner [EMAIL PROTECTED] wrote:
On Wed, Dec 13, 2006 at 02:12:23PM +0900, Shinichiro HIDA wrote:
Hi,
I met same problem on my 2
On Wed, 13 Dec 2006 10:59:11 +1100
NeilBrown [EMAIL PROTECTED] wrote:
From: Chuck Lever [EMAIL PROTECTED]
Expand the rq_addr field to allow it to contain larger addresses.
This patch breaks the NFS server on my heroically modern RH FC1 machine.
There's a mysterious 30-second pause when
On Dec 14, 2006, Greg KH [EMAIL PROTECTED] wrote:
I think you missed the point that my patch prevents valid usages of
non-GPL modules from happening, which is not acceptable.
What if you changed your patch so as to only permit loading of
possibly-infringing drivers after some flag in /proc is
On Wed, 6 Dec 2006 16:59:35 +
Andy Whitcroft [EMAIL PROTECTED] wrote:
+ tmp = __pfn_to_page(pfn);
ia64 doesn't implement __page_to_pfn. Why did you not use page_to_pfn()?
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to
On Wed, 13 Dec 2006 22:26:26 +0100
Eric Dumazet [EMAIL PROTECTED] wrote:
This patch introduces a new structure called time_data, where some time
keeping related variables are put together to share as few cache lines as
possible.
ia64 refers to xtime_lock from assembly and hence doesn't
On Dec 14, 2006, Jeff V. Merkey [EMAIL PROTECTED] wrote:
FREE implies a transfer of ownsership
It's about freedom, not price. And even then, it's the license that
has not cost, not the copyright.
and you also have to contend with the Doctrine of Estoppel. i.e. if
someone has been using the
Associate function calls with significant events in a task's lifetime much like
we handle kernel and module init/exit functions. This creates a table for each
of the following events in the task_watchers_table ELF section:
WATCH_TASK_INIT at the beginning of a fork/clone system call when the
new
This is version 2 of my Task Watchers patches with performance enhancements.
Task watchers calls functions whenever a task forks, execs, changes its
[re][ug]id, or exits.
Task watchers is primarily useful to existing kernel code as a means of making
the code in fork and exit more readable.
Make the keyring code use a task watcher to initialize and free per-task data.
NOTE:
We can't make copy_thread_group_keys() in copy_signal() a task watcher because
it needs the task's signal field (struct signal_struct).
Signed-off-by: Matt Helsley [EMAIL PROTECTED]
Cc: David Howells [EMAIL
Change audit to register a task watcher function rather than modify
the copy_process() and do_exit() paths directly.
Removes an unlikely() hint from kernel/exit.c:
if (unlikely(tsk-audit_context))
audit_free(tsk);
This use of unlikely() is an artifact of audit_free()'s
Prefetch the entire array of function pointers.
Signed-off-by: Matt Helsley [EMAIL PROTECTED]
---
kernel/task_watchers.c |2 ++
1 file changed, 2 insertions(+)
Index: linux-2.6.19/kernel/task_watchers.c
===
---
Register an irq-flag-tracing task watcher instead of hooking into
copy_process().
Signed-off-by: Matt Helsley [EMAIL PROTECTED]
---
kernel/fork.c | 19 ---
kernel/irq/handle.c | 24
2 files changed, 24 insertions(+), 19 deletions(-)
Index:
Make the Process events connector use task watchers instead of hooking the
paths it's interested in.
Signed-off-by: Matt Helsley [EMAIL PROTECTED]
---
drivers/connector/cn_proc.c | 51 +++-
fs/exec.c |1
include/linux/cn_proc.h
Register a task watcher for lockdep instead of hooking into copy_process().
Signed-off-by: Matt Helsley [EMAIL PROTECTED]
---
kernel/fork.c|5 -
kernel/lockdep.c | 11 +++
2 files changed, 11 insertions(+), 5 deletions(-)
Index: linux-2.6.19/kernel/fork.c
Register a NUMA mempolicy task watcher instead of hooking into
copy_process() and do_exit() directly.
Signed-off-by: Matt Helsley [EMAIL PROTECTED]
---
kernel/exit.c |4
kernel/fork.c | 15 +--
mm/mempolicy.c | 25 +
3 files changed, 26
Register a task watcher for cpusets instead of hooking into
copy_process() and do_exit() directly.
Signed-off-by: Matt Helsley [EMAIL PROTECTED]
Cc: Paul Jackson [EMAIL PROTECTED]
---
include/linux/cpuset.h |4
kernel/cpuset.c| 11 +--
kernel/exit.c |2 --
Make the semaphore undo code use a task watcher instead of hooking into
copy_process() and do_exit() directly.
Signed-off-by: Matt Helsley [EMAIL PROTECTED]
---
include/linux/sem.h | 17 -
ipc/sem.c | 12
kernel/exit.c |2 --
kernel/fork.c
Nikolai Joukov wrote:
We started the project in April 2004. Right now I am using it as my
/home/kolya file system at home. We believe that at this stage RAIF
is mature enough for others to try it out. The code is available at:
ftp://ftp.fsl.cs.sunysb.edu/pub/raif/
The
Nikolai Joukov wrote:
Nikolai Joukov wrote:
We have designed a new stackable file system that we called RAIF:
Redundant Array of Independent Filesystems.
Great!
We have performed some benchmarking on a 3GHz PC with 2GB of RAM and
U320 SCSI disks. Compared to the Linux RAID
Can some one explain why I see the below crash on Intel Xeon SMP box.
The kernel version is 2.6.11. This is what I'm trying to do in the
driver.
1.Submit a request to a device in 'unlocked_ioctl()' and issue
'wait_event_interruptible_timeout()' for 10 jiffies. There can be many
such outstanding
Andrew Morton a écrit :
On Wed, 13 Dec 2006 16:12:46 -0800
Greg KH <[EMAIL PROTECTED]> wrote:
Original comment seemed to indicate that this conditional thing was
performance related. Is it really? If not, we should consider the below patch.
Yes, it's a performance gain and I don't see how
> Someone also mentioned that we could just put a nice poem into the
> kernel module image in order to be able to enforce our copyright license
> in any court of law.
>
> Full bellies of fish
> Penguins sleep under the moon
> Dream of wings that fly
>
> thanks,
Whoever says
Eric W. Biederman wrote:
What is the problem you are trying to solve?
2 problems
1) irq's that irqbalance should not touch at all
2) irqs that can only go to a subset of processors.
1) is very real today
2) is partially real on some of the bigger numa stuff already.
-
To unsubscribe from this
On Wed, 13 Dec 2006, Martin J. Bligh wrote:
> The point of banning binary drivers would be to leverage hardware
> companies into either releasing open source drivers, or the specs for
> someone else to write them.
IMHO, it's up to the users to decide if they want to keep buying hardware
which
>with the patch it boots perfectly without any command-line args.
Are you getting the 'Firmware space is locked read-only' message then?
Thanks, Jan
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at
On Wed, 2006-12-13 at 16:55 -0800, Greg KH wrote:
> Oh, and for those who have asked me how we would enforce this after this
> date if this decision is made, I'd like to go on record that I will be
> glad to take whatever legal means necessary to stop people from
> violating this.
I see no
On Wed, 2006-12-13 at 20:15 -0800, Linus Torvalds wrote:
> If a module arguably isn't a derived work, we simply shouldn't try to say
> that its authors have to conform to our worldview.
I wouldn't argue that _anyone_ else should be exposed to my worldview; I
think the Geneva Convention has
Arjan van de Ven <[EMAIL PROTECTED]> writes:
> Eric W. Biederman wrote:
>> What is the problem you are trying to solve?
>
> 2 problems
> 1) irq's that irqbalance should not touch at all
This is easy we just need a single bit. Not 128+ bytes on the huge
machines.
> 2) irqs that can only go to a
Eric W. Biederman wrote:
1) is very real today
2) is partially real on some of the bigger numa stuff already.
You have said you the NUMA cases is handled in another way already?
the numa case of "I prefer that cpu" is handled. Not the "I cannot
work on those".
-
To unsubscribe from this
> "Eike" == Rolf Eike Beer <[EMAIL PROTECTED]> writes:
Eike> Am Mittwoch, 13. Dezember 2006 17:51 schrieb
Eike> [EMAIL PROTECTED]:
>> I'm not sure about the driver being cpqfc, I know in 2.6.0 & 1 the
>> driver was definitely iphase.c/h/o I do know the chipset was used
>> by almost everyone,
> > I'll put a .config and a dmesg of the machine booting at
> > http://www.jdi-ict.nl/plain/ for those who want to look at it.
>
> dmesg : http://www.jdi-ict.nl/plain/lnx01.dmesg
> Kernel config : http://www.jdi-ict.nl/plain/lnx01.config
Hmm.. Switching CONFIG_HZ from 1000 to 250 seems to
i've posted on this before so here's a slightly-updated patch that
uses the kbuild "menuconfig" feature to make numerous entries under
the Device drivers menu selectable on the spot. if folks think this
is a good idea, what's the best way to get it in?
i could officially submit the patch as
Arjan van de Ven <[EMAIL PROTECTED]> writes:
> Eric W. Biederman wrote:
>>> 1) is very real today
>>> 2) is partially real on some of the bigger numa stuff already.
>>
>> You have said you the NUMA cases is handled in another way already?
>
> the numa case of "I prefer that cpu" is handled. Not
Description.
diff --git a/Documentation/kevent.txt b/Documentation/kevent.txt
new file mode 100644
index 000..2e03a3f
--- /dev/null
+++ b/Documentation/kevent.txt
@@ -0,0 +1,240 @@
+Description.
+
+int kevent_init(struct kevent_ring *ring, unsigned int ring_size,
+ unsigned int
Socket notifications.
This patch includes socket send/recv/accept notifications.
Using trivial web server based on kevent and this features
instead of epoll it's performance increased more than noticebly.
More details about various benchmarks and server itself
(evserver_kevent.c) can be found
Timer notifications.
Timer notifications can be used for fine grained per-process time
management, since interval timers are very inconvenient to use,
and they are limited.
This subsystem uses high-resolution timers.
id.raw[0] is used as number of seconds
id.raw[1] is used as number of
Generic event handling mechanism.
Kevent is a generic subsytem which allows to handle event notifications.
It supports both level and edge triggered events. It is similar to
poll/epoll in some cases, but it is more scalable, it is faster and
allows to work with essentially eny kind of events.
poll/select() notifications.
This patch includes generic poll/select notifications.
kevent_poll works simialr to epoll and has the same issues (callback
is invoked not from internal state machine of the caller, but through
process awake, a lot of allocations and so on).
Signed-off-by: Evgeniy
Pipe notifications.
diff --git a/fs/pipe.c b/fs/pipe.c
index f3b6f71..aeaee9c 100644
--- a/fs/pipe.c
+++ b/fs/pipe.c
@@ -16,6 +16,7 @@
#include
#include
#include
+#include
#include
#include
@@ -312,6 +313,7 @@ redo:
break;
}
Kevent posix timer notifications.
Simple extensions to POSIX timers which allows
to deliver notification of the timer expiration
through kevent queue.
Example application posix_timer.c can be found
in archive on project homepage.
Signed-off-by: Evgeniy Polyakov <[EMAIL PROTECTED]>
diff --git
On Thu, 14 Dec 2006, Jan Beulich wrote:
> >with the patch it boots perfectly without any command-line args.
>
> Are you getting the 'Firmware space is locked read-only' message then?
yep...
so let me ask a naive question... don't we want the firmware locked
read-only because that protects the
> > the numa case of "I prefer that cpu" is handled. Not the "I cannot work on
> > those".
>
> How is the NUMA case of I prefer that cpu handled?
it's exported via /sys/bus/pci/devices//local_cpus
(and the irq is in the /irq directory next to local_cpus)
-
To unsubscribe from this list: send
On Thu, 14 Dec 2006 09:15:39 +0100 (CET)
Igmar Palsenberg <[EMAIL PROTECTED]> wrote:
>
> > > I'll put a .config and a dmesg of the machine booting at
> > > http://www.jdi-ict.nl/plain/ for those who want to look at it.
> >
> > dmesg : http://www.jdi-ict.nl/plain/lnx01.dmesg
> > Kernel config :
On Thu, Dec 14, 2006 at 12:10:15AM -0500, Bill Nottingham wrote:
>
> Greg KH ([EMAIL PROTECTED]) said:
> > An updated version is below.
>
> If you're adding this, you should probably schedule EXPORT_SYMBOL_GPL
> for removal at the same time, as this essentially renders that irrelevant.
>
>
On Tue, 12 Dec 2006, Randy Dunlap wrote:
> On Tue, 12 Dec 2006 07:48:51 +0100 (CET) Ben Castricum wrote:
>
> >
> > This bug started to show up after the release of 2.6.19 (iirc plain 2.6.19
> > was still working fine).
> >
> > The full dmesg is at
> >
> > Hmm.. Switching CONFIG_HZ from 1000 to 250 seems to 'fix' the problem.
> > I haven't seen the issue in nearly a week now. This makes Andrew's theory
> > about missing interrupts very likely.
> >
> > Andrew / others : Is there a way to find out if it *is* missing
> > interrupts ?
> >
>
>
> I'm really not convinced about the user-mode thing unless somebody can
> show me a good reason for it. Not just some "wouldn't it be nice" kind of
> thing. A real, honest-to-goodness reason that we actually _want_ to see
> used.
Qemu? It would be nice if emulators could directly drive
On Thu, 14 Dec 2006 06:56:24 +
Al Viro <[EMAIL PROTECTED]> wrote:
> On Thu, Dec 14, 2006 at 06:44:30AM +, Al Viro wrote:
> > On Wed, Dec 13, 2006 at 10:10:05PM -0500, Ben Collins wrote:
> > > At least on PPC, the "op ? op : dma" construct causes a compile failure
> > > because the dma_*
On Thu, 14 Dec 2006 09:55:38 +0100 (CET)
Igmar Palsenberg <[EMAIL PROTECTED]> wrote:
>
> > > Hmm.. Switching CONFIG_HZ from 1000 to 250 seems to 'fix' the problem.
> > > I haven't seen the issue in nearly a week now. This makes Andrew's theory
> > > about missing interrupts very likely.
> > >
On Wed, 2006-12-13 at 23:56 +, Alan wrote:
> On Wed, 13 Dec 2006 23:30:55 +0100
> Thomas Gleixner <[EMAIL PROTECTED]> wrote:
>
> > - IRQ happens
> > - kernel handler runs and masks the chip irq, which removes the IRQ
> > request
>
> IRQ is shared with the disk driver, box dead.
Err ?
IRQ
On Wed, Dec 13, 2006 at 09:34:16PM +0100, Karsten Weiss wrote:
> FWIW: As far as I understand the linux kernel code (I am no kernel
> developer so please correct me if I am wrong) the PCI dma mapping code is
> abstracted by struct dma_mapping_ops. I.e. there are currently four
> possible
> > See below. The other machine is mostly identifical, except for i8042
> > missing (probably due to running an older kernel, or small differences in
> > the kernel config).
> >
>
> Does the other machine have the same problems?
No, but that machine has a lot less disk and networkactivity.
On Wed, Dec 13, 2006 at 01:29:25PM -0700, Erik Andersen wrote:
> On Mon Dec 11, 2006 at 10:24:02AM +0100, Karsten Weiss wrote:
> > We could not reproduce the data corruption anymore if we boot
> > the machines with the kernel parameter "iommu=soft" i.e. if we
> > use software bounce buffering
On Thu, Dec 14, 2006 at 12:33:23AM +0100, Christoph Anton Mitterer wrote:
> 4)
> And does someone know if the nforce/opteron iommu requires IBM Calgary
> IOMMU support?
It doesn't, Calgary isn't found in machine with Opteron CPUs or NForce
chipsets (AFAIK). However, compiling Calgary in should
On Wed, Dec 13, 2006 at 10:15:47PM +0100, Arjan van de Ven wrote:
> with DRI you have the case where "something" needs to do security
> validation of the commands that are sent to the card. (to avoid a
> non-privileged user to DMA all over your memory)
We also have the interesting case where
On Wed, Dec 13, 2006 at 09:11:29PM +0100, Christoph Anton Mitterer wrote:
> - error in the Opteron (memory controller)
> - error in the Nvidia chipsets
> - error in the kernel
My guess without further information would be that some, but not all
BIOSes are doing some work to avoid this.
Does
Fix do_page_fault and update_mmu_cache.
* Fix do_page_fault (vmalloc_fault:) to pass error_code correctly
to update_mmu_cache by using a thread-fault code for all m32r chips.
* Fix update_mmu_cache for OPSP chip
- #ifdef CONFIG_CHIP_OPSP portion is a workaround of OPSP;
Add a
This patch fixes the kernel entry point address of vmlinux.
The m32r kernel entry address is 0x08002000 (physical).
But, so far, the ENTRY point written in vmlinux.lds.S was not point
the correct kernel entry address.
(before fix)
$ objdump -x vmlinux
vmlinux: file format
Cosmetic updates and trivial fixes of m32r arch-dependent files.
- Remove RCS ID strings and trailing white lines
- Other misc. cosmetic updates
Signed-off-by: Hirokazu Takata <[EMAIL PROTECTED]>
---
arch/m32r/kernel/head.S |2 --
arch/m32r/lib/ashxdi3.S |
Dear Linux developers,
I recently discovered that the Linux kernel on 32 bits x86 processors
reports the stack as being non-executable while it is actually
executable (because located in the same memory segment).
# grep maps /proc/self/maps
bfce8000-bfcfe000 rw-p bfce8000 00:00 0
On Thu Dec 14, 2006 at 11:23:11AM +0200, Muli Ben-Yehuda wrote:
> > I just realized that booting with "iommu=soft" makes my pcHDTV
> > HD5500 DVB cards not work. Time to go back to disabling the
> > memhole and losing 1 GB. :-(
>
> That points to a bug in the driver (likely) or swiotlb
On Thu, 2006-12-14 at 10:26 +0100, Franck Pommereau wrote:
> Dear Linux developers,
>
> I recently discovered that the Linux kernel on 32 bits x86 processors
> reports the stack as being non-executable while it is actually
> executable (because located in the same memory segment).
this is not
On Thu, Dec 14, 2006 at 02:52:35AM -0700, Erik Andersen wrote:
> On Thu Dec 14, 2006 at 11:23:11AM +0200, Muli Ben-Yehuda wrote:
> > > I just realized that booting with "iommu=soft" makes my pcHDTV
> > > HD5500 DVB cards not work. Time to go back to disabling the
> > > memhole and losing 1 GB.
Greetings,
Lockdep doesn't approve of cpufreq, and seemingly with cause... I had to
poke SysRq-O.
[ 1103.164377] Disabling non-boot CPUs ...
[ 1103.171094] stopped custom tracer.
[ 1103.174614]
[ 1103.174618] ===
[ 1103.182692] [ INFO:
Additional fixes for processors without ISA_DSP_LEVEL2.
sigcontext_t does not have dummy_acc1h, dummy_acc1l members any longer.
This patch is against v2.6.19.1 kernel.
From: Hirokazu Takata <[EMAIL PROTECTED]>
Subject: [PATCH 2.6.19] m32r: Make userspace headers platform-independent
Date: Wed,
* Mike Galbraith <[EMAIL PROTECTED]> wrote:
> Greetings,
>
> Lockdep doesn't approve of cpufreq, and seemingly with cause... I had
> to poke SysRq-O.
hm ... this must be an upstream problem too, right? -rt shouldnt change
anything in this area (in theory).
Ingo
-
To unsubscribe from
Greg KH wrote:
A large number of people have expressed interest recently in the
userspace i/o driver core which allows userspace drivers to be written
to handle some types of hardware.
Right now the UIO core is working and in the -mm releases. It's been
rewritten from the last time patches
* tike64 <[EMAIL PROTECTED]> wrote:
> Steven Rostedt <[EMAIL PROTECTED]> wrote:
> > Also, have you tried this with a nanosleep instead of a select.
> > Select's timeout is just that, a timeout. It's not suppose to be
> > accurate, as long as it doesn't expire early. The reason I state
> > this,
On Thu, 2006-12-14 at 10:59 +0100, Ingo Molnar wrote:
> * Mike Galbraith <[EMAIL PROTECTED]> wrote:
>
> > Greetings,
> >
> > Lockdep doesn't approve of cpufreq, and seemingly with cause... I had
> > to poke SysRq-O.
>
> hm ... this must be an upstream problem too, right? -rt shouldnt change
>
>>> dean gaudet <[EMAIL PROTECTED]> 14.12.06 09:40 >>>
>On Thu, 14 Dec 2006, Jan Beulich wrote:
>
>> >with the patch it boots perfectly without any command-line args.
>>
>> Are you getting the 'Firmware space is locked read-only' message then?
>
>yep...
>
>so let me ask a naive question... don't
Am Donnerstag, 14. Dezember 2006 10:30 schrieb Muli Ben-Yehuda:
> On Wed, Dec 13, 2006 at 10:15:47PM +0100, Arjan van de Ven wrote:
>
> > with DRI you have the case where "something" needs to do security
> > validation of the commands that are sent to the card. (to avoid a
> > non-privileged user
> I understand one still has to write a kernel driver to shut up the irq.
> How about writing a small bytecode interpreter to make event than
> unnecessary?
if you do that why not do a real driver.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a
Version is 2.6.19-rc6-git. System was more or less idle, just normal desktop
stuff (copying single files by scp, writing mail). Don't know what exactly
was working when this happened, I saw it some minutes later.
BUG: warning at fs/inotify.c:181/set_dentry_child_flags()
[]
Am Donnerstag, 14. Dezember 2006 10:44 schrieb Avi Kivity:
>
> I understand one still has to write a kernel driver to shut up the irq.
> How about writing a small bytecode interpreter to make event than
> unnecessary?
>
> The userspace driver would register a couple of bytecode programs:
>
On Thu, 14 Dec 2006 01:35:17 +0100 (CET)
Jiri Slaby <[EMAIL PROTECTED]> wrote:
> isicom, remove tty_{hang,wake}up bottomhalves
>
> - tty_hangup() itself schedules work, so there is no need to schedule hangup
> in the driver
> - tty_wakeup() its safe to call it while in atomic (IS THIS
> 2008? I bet a lot of people would read the above to say that their
> system will just drop dead of a New Year's hangover, and they'll freak.
> I wouldn't want to be the one getting all the email at that point...
I wouldn't worry. Everyone will have patched it back out again by then,
or made
Ingo Molnar <[EMAIL PROTECTED]> wrote:
> tike64 <[EMAIL PROTECTED]> wrote:
> > Ok, understood; I tried this:
> >
> > t = raw_timer();
> > ts.tv_nsec = 500;
> > ts.tv_sec = 0;
> > nanosleep(, 0);
> > t = raw_timer() - t;
> >
> > It is better but I still see 8ms occasional
Am Donnerstag, 14. Dezember 2006 09:49 schrieb Duncan Sands:
> > I'm really not convinced about the user-mode thing unless somebody can
> > show me a good reason for it. Not just some "wouldn't it be nice" kind of
> > thing. A real, honest-to-goodness reason that we actually _want_ to see
> >
> But in order to get this core into the kernel tree, we need to have some
> "real" drivers written that use it. So, for anyone that wants to see
> this go into the tree, now is the time to step forward and post your
> patches for hardware that this kind of driver interface is needed.
Might be
Arjan van de Ven wrote:
I understand one still has to write a kernel driver to shut up the irq.
How about writing a small bytecode interpreter to make event than
unnecessary?
if you do that why not do a real driver.
An entire driver in bytecode? that means exposing the entire
On Wed, 13 Dec 2006 17:17:45 -0800 (PST)
Doug Thompson <[EMAIL PROTECTED]> wrote:
> From: Mike Chan <[EMAIL PROTECTED]>
>
> Diff against 2.6.19
>
> This fix/change returns the offset into the page for
> the ce/ue error, instead of just 0. The e752x dram controller reads
> 34:6 of the
> linear
> +void edac_mc_handle_fbd_ue(struct mem_ctl_info *mci,
> + unsigned int csrow,
> + unsigned int channela,
> + unsigned int channelb,
> + char *msg)
> +{
> + int len =
[why trim the cc?]
Hans-Jürgen Koch wrote:
Am Donnerstag, 14. Dezember 2006 10:44 schrieb Avi Kivity:
I understand one still has to write a kernel driver to shut up the irq.
How about writing a small bytecode interpreter to make event than
unnecessary?
The userspace driver would
On Wed, 13 Dec 2006 17:18:53 -0800 (PST)
Doug Thompson <[EMAIL PROTECTED]> wrote:
> From: Frithiof Jensen <[EMAIL PROTECTED]>
>
> This patch is meant for Kernel version 2.6.19
>
> This is an attempt of providing an interface for memory
> scrubbing control in EDAC.
> Signed-off-by:
On Thu, 2006-12-14 at 12:46 +0200, Avi Kivity wrote:
> Arjan van de Ven wrote:
> >> I understand one still has to write a kernel driver to shut up the irq.
> >> How about writing a small bytecode interpreter to make event than
> >> unnecessary?
> >>
> >
> > if you do that why not do a real
Arjan van de Ven wrote:
On Thu, 2006-12-14 at 12:46 +0200, Avi Kivity wrote:
Arjan van de Ven wrote:
I understand one still has to write a kernel driver to shut up the irq.
How about writing a small bytecode interpreter to make event than
unnecessary?
if you do that
401 - 500 of 871 matches
Mail list logo
