On Wednesday 21 November 2007 06:07, Arjan van de Ven wrote:
> On Wed, 21 Nov 2007 02:43:46 +1100
> > Of course it is, if you want to effectively use your resources.
> > Imagine if the task balancer only polled once every 10s.
>
> but unlike the task balancer, moving an irq is really expensive.
>
On Tue, Nov 20, 2007 at 10:47:52PM +0100, Dmitry Adamushko wrote:
> btw., what's your system? If I recall right, SD_BALANCE_NEWIDLE is on
> by default for all configs, except for NUMA nodes.
It's a dual AMD64 Opteron.
So, I recompiled my 2.6.23.1 kernel without NUMA support, and with
your patch
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Serge E. Hallyn wrote:
> The problem is that when you run a setuid binary, its pP and pE are
> fully raised. The following patch fixes it for me. Chris, does it fix
> your problem? Andrew, am I again confusing myself and doing something
> unsafe?
Build kernel 2.6.24-rc3, cat /proc/cpuinfo, all processor items show "0":
processor : 0
vendor_id : GenuineIntel
cpu family : 15
model : 6
model name :Genuine Intel(R) CPU 3.40GHz
stepping: 8
cpu MHz : 3391.555
cache size
Zachary Amsden wrote:
On Wed, 2007-11-21 at 09:13 +0200, Avi Kivity wrote:
Where the device is implemented is an implementation detail that should
be hidden from the guest, isn't that one of the strengths of
virtualization? Two examples: a file-based block device implemented in
qemu
On Thu, Nov 22, 2007 at 02:41:06PM +1100, David Chinner wrote:
> On Wed, Nov 21, 2007 at 08:57:27PM -0600, Matt Mackall wrote:
> > On Thu, Nov 22, 2007 at 12:12:14PM +1100, David Chinner wrote:
> > > In all the cases that I know of where ppl are using what could
> > > be considered real-time I/O
Hi all,
some upates about this issue (see also bug 9147
http://bugzilla.kernel.org/show_bug.cgi?id=9147 ).
The 'ac', 'battery' and 'thermal' modules (compiled as stand-alone) do
cause the bug; it suffices that one of them (or any set of them) is
loaded to trigger the bug either immediately
Hello, Robert.
Robert Hancock wrote:
> This fixes some problems with ATAPI devices on nForce4 controllers in ADMA
> mode on systems with memory located above 4GB. We need to delay setting the
> 64-bit DMA mask until the PRD table and padding buffer are allocated so that
> they don't get allocated
On Tue, Nov 20, 2007 at 12:29:03PM -0800, Dave Bailey wrote:
> This problem has been around since kernel 2.6.16, and I see it in
> 2.6.23.1-10.fc7. It occurs in the ufs_check_page function of ufs/dir.c
> at the Espan test, which seems unnecessary for NextStep/OpenStep
> files systems. The
On Mon, Nov 19, 2007 at 05:53:36PM -0800, Joe Perches wrote:
>
> Signed-off-by: Joe Perches <[EMAIL PROTECTED]>
> ---
> fs/ufs/dir.c |2 +-
> 1 files changed, 1 insertions(+), 1 deletions(-)
>
> diff --git a/fs/ufs/dir.c b/fs/ufs/dir.c
> index 30f8c2b..d19dfe8 100644
> --- a/fs/ufs/dir.c
>
On Thu, 2007-11-22 at 12:12 +1100, David Chinner wrote:
> In all the cases that I know of where ppl are using what could
> be considered real-time I/O (e.g. media environments where they
> do real-time ingest and playout from the same filesystem) the
> real-time ingest processes create the files
On Thursday 22 November 2007 13:43:06 Andi Kleen wrote:
> There seems to be rough consensus that the kernel currently has too many
> exported symbols. A lot of these exports are generally usable utility
> functions or important driver interfaces; but another large part are
> functions intended by
It seems that a process blocked in a write to an xfs filesystem due to
xfs_freeze cannot be frozen by the freezer.
I see this if I suspend my laptop while doing something xfs-filesystem
intensive, like a kernel build. My suspend scripts freeze the XFS
filesystem (as Dave said I should), which
On Thu, Nov 22, 2007 at 03:43:06AM +0100, Andi Kleen wrote:
> There seems to be rough consensus that the kernel currently has too many
> exported symbols. A lot of these exports are generally usable utility
> functions or important driver interfaces; but another large part are
> functions
On Thu, Nov 15, 2007 at 01:14:32PM -0800, Linus Torvalds wrote:
> Examples of non-broken solutions:
> (a) always use lowmem sizes (what we do now)
> (b) always use total mem sizes (sane but potentially dangerous: but the
> VM pressure should work! It has serious bounce-buffer issues,
On Wed, Nov 21, 2007 at 08:57:27PM -0600, Matt Mackall wrote:
> On Thu, Nov 22, 2007 at 12:12:14PM +1100, David Chinner wrote:
> > In all the cases that I know of where ppl are using what could
> > be considered real-time I/O (e.g. media environments where they
> > do real-time ingest and playout
RCU style multiple probes support for the Linux Kernel Markers.
Common case (one probe) is still fast and does not require dynamic allocation
or a supplementary pointer dereference on the fast path.
- Move preempt disable from the marker site to the callback.
Since we now have an internal
> I like this concept in general; I have one minor comment; right now
> your namespace argument is like
>
> EXPORT_SYMBOL_NS(foo, some_symbol);
>
> from a language-like pov I kinda wonder if it's nicer to do
>
> EXPORT_SYMBOL_NS("foo", some_symbol);
>
> because foo isn't something in C scope,
On Thu, Nov 22, 2007 at 11:15:55AM +0800, Shi Weihua wrote:
> This patch removes some redundant code in the function setup_sigcontext().
>
> The registers ar.ccv,b7,r14,ar.csd,ar.ssd,r2-r3 and r16-r31 are not restored
> in restore_sigcontext() when (flags & IA64_SC_FLAG_IN_SYSCALL) is true.
>
This patch removes some redundant code in the function setup_sigcontext().
The registers ar.ccv,b7,r14,ar.csd,ar.ssd,r2-r3 and r16-r31 are not restored
in restore_sigcontext() when (flags & IA64_SC_FLAG_IN_SYSCALL) is true.
So we don't need to zero those variables in setup_sigcontext().
On Wed, 21 Nov 2007 00:49:09 -0800
Andrew Morton <[EMAIL PROTECTED]> wrote:
> On Wed, 21 Nov 2007 17:42:15 +0900 KAMEZAWA Hiroyuki <[EMAIL PROTECTED]>
> wrote:
>
> > Hi, Andrew
> >
> > I got following result in 'sync' command.
> > It was too slow. (memory controller config is off ;)
> > I
On Thu, 22 Nov 2007 03:43:06 +0100 (CET)
Andi Kleen <[EMAIL PROTECTED]> wrote:
>
> There seems to be rough consensus that the kernel currently has too
> many exported symbols. A lot of these exports are generally usable
> utility functions or important driver interfaces; but another large
> part
On Thu, Nov 22, 2007 at 12:12:14PM +1100, David Chinner wrote:
> On Thu, Nov 22, 2007 at 01:49:25AM +0100, Andi Kleen wrote:
> > David Chinner <[EMAIL PROTECTED]> writes:
> >
> > > To ensure that log I/O is issued as the highest priority I/O, set
> > > the I/O priority of the log I/O to the
Simon Holm Thøgersen wrote:
ons, 21 11 2007 kl. 20:52 -0500, skrev Jie Chen:
There is a backport of the CFS scheduler to 2.6.21, see
http://lkml.org/lkml/2007/11/19/127
Hi, Simon:
I will try that after the thanksgiving holiday to find out whether the
odd behavior will show up using 2.6.21
On Wed, 21 Nov 2007 17:08:30 -0800
Al Niessner <[EMAIL PROTECTED]> wrote:
>
> Lastly, I would be happy to give out the entire module to anyone who
> requests it, but it is about 550 lines so I did not want to attach it
> to this already long post.
>
can you send it to me, or even better, post
In article <[EMAIL PROTECTED]> (at Thu, 22 Nov 2007 10:34:03 +0800), Herbert Xu
<[EMAIL PROTECTED]> says:
> On Wed, Nov 21, 2007 at 07:17:40PM -0500, Jeff Garzik wrote:
> >
> > For those interested, I am dealing with a UDP app that already does very
> > strong checksumming and encryption, so
On Wed, 21 Nov 2007 12:26:55 +0100
Jens Axboe <[EMAIL PROTECTED]> wrote:
> On Tue, Nov 20 2007, FUJITA Tomonori wrote:
> > pci-noop.c doesn't use DMA mappings.
>
> you should send that one to the alpha maintainers, it needs to go in
> that way.
Yeah, I'll do.
-
To unsubscribe from this list:
This patch makes swiotlb not allocate a memory area spanning LLD's
segment boundary.
is_span_boundary() judges whether a memory area spans LLD's segment
boundary. If map_single finds such a area, map_single tries to find
the next available memory area.
Signed-off-by: FUJITA Tomonori <[EMAIL
This is the latter half of my iommu work to make the IOMMUs respect
LLDs restrictions.
IOMMUs allocate memory areas without considering a low level driver's
segment boundary limits. So we have some workarounds: splitting sg
segments again in LLDs; reserving all I/O space spanning 4GB boundary
in
This adds new accessors for segment_boundary_mask in
device_dma_parameters structure in the same way I did for
max_segment_size. So we can easily change where to place struct
device_dma_parameters in the future.
dma_get_segment boundary returns 0x if dma_parms in struct
device isn't set
This is a one-line patch to add the following to __scsi_alloc_queue():
dma_set_seg_boundary(dev, shost->dma_boundary);
This is the simplest approach but the result looks odd,
__scsi_alloc_queue() does:
blk_queue_segment_boundary(q, shost->dma_boundary);
dma_set_seg_boundary(dev,
This adds PCI's accessor for segment_boundary_mask in
device_dma_parameters.
The default segment_boundary is set to 0x, same to the block
layer's default value (and the scsi mid layer uses the same value).
Signed-off-by: FUJITA Tomonori <[EMAIL PROTECTED]>
---
drivers/pci/pci.c |8
I defined two namespaces: tcp for TCP internals which are only used by
tcp_ipv6.ko And tcpcong for exports used by the TCP congestion modules
No need to export any TCP internals to anybody else. So express this in a
namespace.
I admit I'm not 100% sure tcpcong makes sense -- there might be a
Shared by IP, IPv6, DCCP, UDPLITE, SCTP.
The symbols used by tunnel modules weren't put into any name space
because there are quite a lot of them.
---
net/core/fib_rules.c|9 --
net/ipv4/af_inet.c | 52
net/ipv4/arp.c
The UDP exports are only used by UDPv6 and UDP lite. They are internal functions
not supposed to be used by anybody else. So turn them into a name space that
only allows those.
---
net/ipv4/udp.c | 27 +++
net/ipv4/udplite.c |6 +++---
2 files changed, 18
When passing an file name > 1k the stack could be overflowed.
Not really a security issue, but still better plugged.
---
scripts/mod/modpost.c |3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
Index: linux/scripts/mod/modpost.c
This checks the namespaces at build time in modpost
---
scripts/mod/modpost.c | 344 ++
1 file changed, 317 insertions(+), 27 deletions(-)
Index: linux/scripts/mod/modpost.c
===
---
Fix wrong format strings in modpost exposed by the previous patch.
Including one missing argument -- some random data was printed instead.
---
scripts/mod/modpost.c |7 ---
1 file changed, 4 insertions(+), 3 deletions(-)
Index: linux/scripts/mod/modpost.c
This way gcc can warn for wrong format strings
---
scripts/mod/modpost.c |8 +---
1 file changed, 5 insertions(+), 3 deletions(-)
Index: linux/scripts/mod/modpost.c
===
--- linux.orig/scripts/mod/modpost.c
+++
This seems to have been forgotten earlier. Right now it was possible
for a normal symbol to override a future gpl symbol and similar.
I restructured the code a bit to avoid too much duplicated code.
---
kernel/module.c | 45 -
1 file changed, 24
There seems to be rough consensus that the kernel currently has too many
exported symbols. A lot of these exports are generally usable utility
functions or important driver interfaces; but another large part are functions
intended by only one or two very specific modules for a very specific
Is there a reason why this isn't allowed now?
---
fs/fcntl.c |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/fs/fcntl.c b/fs/fcntl.c
index 8685263..fc0c92e 100644
--- a/fs/fcntl.c
+++ b/fs/fcntl.c
@@ -203,7 +203,7 @@ asmlinkage long sys_dup(unsigned int fildes)
On Wed, Nov 21, 2007 at 07:17:40PM -0500, Jeff Garzik wrote:
>
> For those interested, I am dealing with a UDP app that already does very
> strong checksumming and encryption, so additional software checksumming
> at the lower layers is quite simply a waste of CPU cycles. Hardware
>
ons, 21 11 2007 kl. 20:52 -0500, skrev Jie Chen:
> Eric Dumazet wrote:
> > Jie Chen a écrit :
> >> Hi, there:
> >>
> >> We have a simple pthread program that measures the synchronization
> >> overheads for various synchronization mechanisms such as spin locks,
> >> barriers (the barrier is
On Wed, Nov 21, 2007 at 05:08:30PM -0800, Al Niessner wrote:
> On with the detailed technical information. I developed a kernel module
> for an PCI card back in 2.4, moved it to 2.6.3, then 2.6.11 or so and
> now I am trying to move it to 2.6.22. When I began the to move to
> 2.6.22, I changed all
On 22/11/2007, Al Niessner <[EMAIL PROTECTED]> wrote:
>
> Quickly stated, I have a piece of hardware on the PCI bus that is
> generating an interrupt (can watch it with a scope) but my handler is
> not being called (no printk in /var/log/messages). So, where has the
> interrupt gone?
>
Just to
On Thu, Nov 22, 2007 at 10:51:15AM +1100, Bron Gondwana wrote:
> On Thu, Nov 15, 2007 at 08:32:22AM -0800, Linus Torvalds wrote:
> > If this patch makes a difference, please holler. I think it's the correct
> > thing to do, but I'm not going to actually commit it without somebody
> > saying that
On Thu, Nov 22, 2007 at 01:56:25AM +, Alan Cox wrote:
> > status = request_irq (apcsi[i].board_irq,
> > apc8620_handler,
> > IRQF_DISABLED,
>
> You set IRQF_DISABLED
>
> Do you then enable the interrupt anywhere
> status = request_irq (apcsi[i].board_irq,
> apc8620_handler,
> IRQF_DISABLED,
You set IRQF_DISABLED
Do you then enable the interrupt anywhere later on ?
Alan
-
To unsubscribe from this list: send the line "unsubscribe
Eric Dumazet wrote:
Jie Chen a écrit :
Hi, there:
We have a simple pthread program that measures the synchronization
overheads for various synchronization mechanisms such as spin locks,
barriers (the barrier is implemented using queue-based barrier
algorithm) and so on. We have dual
Quickly stated, I have a piece of hardware on the PCI bus that is
generating an interrupt (can watch it with a scope) but my handler is
not being called (no printk in /var/log/messages). So, where has the
interrupt gone?
Obligatory information:
1) I have done the google search and mailing list
On Thu, Nov 22, 2007 at 01:49:25AM +0100, Andi Kleen wrote:
> David Chinner <[EMAIL PROTECTED]> writes:
>
> > To ensure that log I/O is issued as the highest priority I/O, set
> > the I/O priority of the log I/O to the highest possible. This will
> > ensure that log I/O is not held up behind bulk
Hi Ian,
Personally I'm very appreciate your patches, they'll will
help submitting HP iPaqs SOCs/MFDs, you know... ;-)
Thus, much thanks in advance.
Few comments...
On Wed, Nov 21, 2007 at 03:54:15AM +, ian wrote:
> On Wed, 2007-11-21 at 10:23 +0800, eric miao wrote:
> > Roughly went
On Thu, Nov 22, 2007 at 12:34:09AM +, ian wrote:
> +void mfd_free_devices(struct platform_device *devices, int nr_devs)
> +{
> + struct platform_device *dev = devices;
> + int i;
> +
> + for (i = 0; i < nr_devs; i++) {
> + struct resource *res = dev->resource;
> +
On Wed, Nov 21, 2007 at 04:45:10AM +0100, Tomasz K?oczko wrote:
>
> BUG: unable to handle kernel NULL pointer dereference at virtual address
> 0014
Did this happen with older versions of 2.6.22.y?
Have you asked the autofs people about this?
thanks,
greg k-h
-
To unsubscribe from this
David Chinner <[EMAIL PROTECTED]> writes:
> To ensure that log I/O is issued as the highest priority I/O, set
> the I/O priority of the log I/O to the highest possible. This will
> ensure that log I/O is not held up behind bulk data or other
> metadata I/O as delaying log I/O can pause the entire
Robert Hancock wrote:
> Tejun Heo wrote:
>> Tejun Heo wrote:
>>> If so, can you please add that switching into register mode is okay as
>>> long as there's no other ADMA commands in flight and add
>>> WARN_ON((qc->flags & ATA_QCFLAG_RESULT_TF) && link->sactive)?
>>
>> More accurately,
Use xfs_inode_clean() in more places.
Signed-off-by: Dave Chinner <[EMAIL PROTECTED]>
---
fs/xfs/xfs_inode.c | 27 +--
fs/xfs/xfs_inode_item.h |8
fs/xfs/xfs_vnodeops.c |4 +---
3 files changed, 14 insertions(+), 25 deletions(-)
Index:
Use RCU locking on the inode radix trees
To make use of the efficient radix tree gang lookups for
inode cluster operations we had to increase the time we hold
the radix tree read lock for. This will affect performance
somewhat.
Given that all the lookups are done on a radix tree and we
already
Use radix_tree_gang_lookup_range() for inode cluster lookups
Now that we have an efficent lookup method for the radix tree,
convert cluster lookups to use it. Factor out the common
lookup, add some debug checking to it and call it where needed.
For sanity, we need to hold the radix tree lock in
Remove the xfs_icluster structure and replace with a radix tree lookup.
We don't need to keep a list of inodes in each cluster around anymore
as we can look them up quickly when we need to. The only time we need
to do this now is during inode writeback.
Factor the inode cluster writeback code
When pdflush is writing back inodes, it can get stuck on inode cluster
buffers that are currently under I/O. This occurs when we write data to
multiple inodes in the same inode cluster at the same time.
Effectively, delayed allocation marks the inode dirty during the data
writeback. Hence if the
On Wed, 2007-11-21 at 12:05 +0800, eric miao wrote:
> On Nov 21, 2007 11:54 AM, ian <[EMAIL PROTECTED]> wrote:
> > On Wed, 2007-11-21 at 10:23 +0800, eric miao wrote:
> > > Roughly went through the patch, looks good, here comes the remind, though
> > > :-)
> > >
> > > 1. is it possible to use
Improve metadata I/O merging in the elevator
Change all async metadata buffers to use [READ|WRITE]_META I/O types
so that the I/O doesn't get issued immediately. This allows merging
of adjacent metadata requests but still prioritises them over bulk
data. This shows a 10-15% improvement in
Factor xfs_itobp() and xfs_inotobp().
The only difference between the functions is one passes an
inode for the lookup, the other passes an inode number.
However, they don't do the same validity checking or set
all the same state on the buffer that is returned yet
they should.
Factor the
Hi,
It seems to me that supplementary groups should be taken into account
when checking for permissions on a tun device. Can someone comment on
my patch below; is it a reasonable approach? If so, I'd like to
submit it for inclusion in the kernel under the GPL.
Please forward any responses to
Reduce log I/O latency
To ensure that log I/O is issued as the highest priority I/O, set
the I/O priority of the log I/O to the highest possible. This will
ensure that log I/O is not held up behind bulk data or other
metadata I/O as delaying log I/O can pause the entire transaction
subsystem.
Introduce radix_tree_gang_lookup_range()
The inode clustering in XFS requires a gang lookup on the radix tree to
find all the inodes in the cluster. The gang lookup has to set the
maximum items to that of a fully populated cluster so we get all the
inodes in the cluster, but we only populate
Normally I wouldn't bother cc'ing lkml on XFS changes, however a
couple of these patches touch generic code. The changes to generic
code are introducing a WRITE_META bio type and
radix_tree_gang_lookup_range() and hence the wider ditribution.
This patch set is against the current xfs-dev tree so
YOSHIFUJI Hideaki / 吉藤英明 wrote:
In article <[EMAIL PROTECTED]> (at Wed, 21 Nov 2007 07:45:32 -0500), Jeff Garzik
<[EMAIL PROTECTED]> says:
SO_NO_CHECK support for IPv6 appeared to be missing. This is presented,
based on a reading of net/ipv4/udp.c.
Disagree. UDP checksum is mandatory in
On Wed, 2007-11-21 at 23:56 +, Roger Leigh wrote:
> Fantastic, thanks! I've copied this to Debian bugs 433236 and 426124
> which were about this problem.
>
> BTW, the framebuffer penguin logo looked a little wierd (low number of
> colours, odd colours), though on my powerpc it has always
Benjamin Herrenschmidt <[EMAIL PROTECTED]> writes:
>> > Can you try the patch from Jean that I pasted below and let us know if
>> > it helps ? It looks like the releasing of the i2c lines may have been
>> > done backward.
>>
>> This patch fixes the problem. The monitor stays powered on during
Wagner Ferenc <[EMAIL PROTECTED]> :
[...]
> So why can I remove a driver serving live network traffic?
Why not ? It is quite common to remove physically a network/storage
device.
--
Ueimor
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
On Thu, Nov 15, 2007 at 08:32:22AM -0800, Linus Torvalds wrote:
> On Thu, 15 Nov 2007, Bron Gondwana wrote:
> >
> > I guess we'll be doing the one-liner kernel mod and testing
> > that then.
>
> The thing to look at is "get_dirty_limits()" in mm/page-writeback.c, and
> in this particular case
Andrew Morton пишет:
> On Thu, 22 Nov 2007 01:49:19 +0300
> Dmitri Vorobiev <[EMAIL PROTECTED]> wrote:
>
>> Zach Brown пишет:
> This doesn't look fine. Did you test this?
Oops, my fault. Of course, I tested the patch, but kernel modules are
disabled in my test setup, so I missed
On Thu, 22 Nov 2007 01:49:19 +0300
Dmitri Vorobiev <[EMAIL PROTECTED]> wrote:
> Zach Brown пишет:
> >>> This doesn't look fine. Did you test this?
> >> Oops, my fault. Of course, I tested the patch, but kernel modules are
> >> disabled in my test setup, so I missed the error.
> >
> > :)
> >
>
On Wed, 2007-11-21 at 18:13 +, Alan Cox wrote:
> > > in the pnp_dev. That is, the resources are tied to the device, with
> > > struct
> > > pnp_resource_table being no more than a handy container to group them
> > > under
> > > a single name.
> > Putting the count into struct resource does
On Wed, 21 Nov 2007 13:36:30 +0530 Kamalesh Babulal <[EMAIL PROTECTED]> wrote:
>
> The kernel build fails on powerpc while linking,
Only for allyesconfig (or maybe some other config that builds a lot of
stuff in.
> AS .tmp_kallsyms3.o
> LD vmlinux.o
> ld: TOC section size exceeds
Zach Brown пишет:
>>> This doesn't look fine. Did you test this?
>> Oops, my fault. Of course, I tested the patch, but kernel modules are
>> disabled in my test setup, so I missed the error.
>
> :)
>
>> Enclosed to this message is a new patch, which replaces the goto-loop by
>> the while-based
The buf in fs/sysfs.c:subsys_attr_store() does not seem to be updated
correctly when returning a negative value (indicating that an error
condition has occurred) is returned. If a negative value is returned,
the next subsequent call to subsys_attr_store will have the contents of
buf appended to
On Wed, 21 Nov 2007 22:45:22 +0100
Laurent Riffard <[EMAIL PROTECTED]> wrote:
> Le 21.11.2007 05:45, Andrew Morton a écrit :
> > ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.24-rc3/2.6.24-rc3-mm1/
>
> Hello,
>
> My system hangs shortly after I logged in Gnome desktop.
This renames arch/x86/ia32/tls32.c to arch/x86/kernel/tls.c, which does
nothing now but paves the way to consolidate this code for 32-bit too.
Signed-off-by: Roland McGrath <[EMAIL PROTECTED]>
---
arch/x86/ia32/Makefile |2 +-
arch/x86/ia32/tls32.c | 158
This consolidates the four different places that implemented the same
encoding magic for the GDT-slot 32-bit TLS support. The old tls32.c was
renamed and is now only slightly modified to be the shared implementation.
Signed-off-by: Roland McGrath <[EMAIL PROTECTED]>
---
> I had a bit of trouble verifying correctness here because of much
> brownian motion. Any possibility of a pure movement / fixup separation
> to make it easier on the eyes?
Yeah, sorry about that. It was late and the whole TLS thing was a sudden
afterthought while I was in the middle of doing
On Wed, 21 Nov 2007 20:35:13 +0200
"Kirill A. Shutemov" <[EMAIL PROTECTED]> wrote:
> Symbol init_level4_pgt is needed by nvidia module. Is it really need to
> unexport it?
It's our clever way of reducing the tester base so we don't get so many
bug reports.
-
To unsubscribe from this list: send
On Wed, 21 Nov 2007 20:23:46 +0200
"Kirill A. Shutemov" <[EMAIL PROTECTED]> wrote:
> USB mouse(Logitech M-BT58) doesn't work. TouchPad works.
> dmesg after rmmod usbcore && modprobe uhci_hcd:
>
> usbcore: registered new interface driver usbfs
> usbcore: registered new interface driver hub
>
On 11/21/07, Laurent Pinchart <[EMAIL PROTECTED]> wrote:
> On Wednesday 21 November 2007, Markus Rechberger wrote:
> > On 11/21/07, Alan Stern <[EMAIL PROTECTED]> wrote:
> > > On Wed, 21 Nov 2007, Markus Rechberger wrote:
> > > > > > it's not just usb_set_interface that hangs actually.
> > > > > >
Stephen Hemminger <[EMAIL PROTECTED]> writes:
> On Wed, 21 Nov 2007 20:45:11 +0100
> Ferenc Wagner <[EMAIL PROTECTED]> wrote:
>
>> Under 2.6.23.1, my lsmod output shows this:
>>
>> $ lsmod | grep tg3
>> tg3 100580 0
>>
>> The usage count is zero, even though it drives my two
Jie Chen a écrit :
Hi, there:
We have a simple pthread program that measures the synchronization
overheads for various synchronization mechanisms such as spin locks,
barriers (the barrier is implemented using queue-based barrier
algorithm) and so on. We have dual quad-core AMD opterons
On Wed, 21 Nov 2007, Laurent Pinchart wrote:
> > > When you suspend, you cut off vbus (afaik, correct me if I'm wrong),
> > > which means your device will get disconnected. One way to avoid this is
> > > enabling CONFIG_USB_PERSIST and trying with that on.
> >
> > Suspend may or may not cut off
On Wed, 21 Nov 2007, Stephen Smalley wrote:
> Do not clear f_op when removing entries since it isn't safe to do.
>
> Signed-off-by: Stephen Smalley <[EMAIL PROTECTED]>
Applied to
git://git.kernel.org/pub/scm/linux/kernel/git/jmorris/selinux-2.6.git#for-akpm
--
James Morris
<[EMAIL
Hi, there:
We have a simple pthread program that measures the synchronization
overheads for various synchronization mechanisms such as spin locks,
barriers (the barrier is implemented using queue-based barrier
algorithm) and so on. We have dual quad-core AMD opterons (barcelona)
clusters
percpu_modcopy is defined multiple times in arch files. However, the only
use is in module.c. Put a static definition into module.c and remove
the definitions from the arch files.
Signed-off-by: Christoph Lameter <[EMAIL PROTECTED]>
---
arch/ia64/kernel/module.c| 10 --
On Thu, 15 Nov 2007 13:47:54 -0800 (PST) Linus Torvalds wrote:
>
>But quite frankly, I refuse to even care about anything past that. If
>you have 12G (or heaven forbid, even more) in your machine, and you
>can't be bothered to just upgrade to a 64-bit CPU, then quite frankly,
>*I* personally
On Wed, Nov 21, 2007 at 11:57:29AM -0800, James Huang wrote:
> Paul,
>
>I am not sure I understand your answer about using test_and_set_bit()
> in tasklet_schedule() as a
> memory barrier in this case.
>
>Yes, tasklet_schedule() includes a
>
On Wed, Nov 21, 2007 at 03:57:53PM -0500, [EMAIL PROTECTED] wrote:
> I have a rather nasty situation developing on one of the big 24x7
> production database servers. It seems that a batch of drives in one of the
> servers started to fail.
>
> The file servers are ext3fs on a top of raid-0 over
Module.c should not define linker variables on its own. We have an include
file for that.
Signed-off-by: Christoph Lameter <[EMAIL PROTECTED]>
---
kernel/module.c |4 +---
1 file changed, 1 insertion(+), 3 deletions(-)
Index: linux-2.6/kernel/module.c
On Wed, 21 Nov 2007 20:45:11 +0100
Ferenc Wagner <[EMAIL PROTECTED]> wrote:
> Hi!
>
> Under 2.6.23.1, my lsmod output shows this:
>
> $ lsmod | grep tg3
> tg3 100580 0
>
> The usage count is zero, even though it drives my two physical
> interfaces:
>
> $ ls -l
On Wed, 21 Nov 2007, Mathieu Desnoyers wrote:
> return -ENOENT;
>
> directly ?
>
> (ERR_PTR() in linux/err.h is a simple cast from long to void*).
Right and there is also IS_ERR_VALUE. Thanks for the feedback. New
version:
Modules: Handle symbols that have a zero value
The module subsystem
Hi,
I have a rather nasty situation developing on one of the big 24x7
production database servers. It seems that a batch of drives in one of the
servers started to fail.
The file servers are ext3fs on a top of raid-0 over a pair of raid-1 mirrors,
with each of raid-1 mirrors having two
1 - 100 of 602 matches
Mail list logo
