On Wed, 15 Aug 2007, Tejun Heo wrote:
> Alan Stern wrote:
> > I think we can simply remove the error message. There's no obvious
> > reason why sysfs_remove_bin_file() should complain about attempts to
> > remove a nonexistent file; sysfs_remove_file() doesn't.
> >
> > This patch will get rid
Cornelia Huck wrote:
> On Wed, 15 Aug 2007 23:54:43 +0900,
> Tejun Heo <[EMAIL PROTECTED]> wrote:
>
>> Alan Stern wrote:
>>> I think we can simply remove the error message. There's no obvious
>>> reason why sysfs_remove_bin_file() should complain about attempts to
>>> remove a nonexistent
On 8/15/07, Stefan Richter <[EMAIL PROTECTED]> wrote:
> Linus Torvalds wrote:
> > #!/bin/sh
> > git log --since=6.months.ago -- "$@" |
> > grep -i '^[-a-z]*by:.*@' |
> > sort | uniq -c |
> > sort -r -n | head
> >
> > and it gives you a
Andi Kleen escreveu:
On Wed, Aug 15, 2007 at 11:25:43AM -0300, Glauber de Oliveira Costa wrote:
On 8/15/07, Andi Kleen <[EMAIL PROTECTED]> wrote:
+#ifdef CONFIG_PARAVIRT
+extern unsigned long *cpu_gdt_descr;
No externs in .c files
Normally they should be where the variable is defined
On Wed, 15 Aug 2007, Florin Iucha wrote:
> On Wed, Aug 15, 2007 at 10:38:54AM -0400, Alan Stern wrote:
> > This patch will get rid of the annoying error messages. It won't do
> > anything about your keyboard's tendency to spontaneously stop working,
> > alas.
>
> My keyboard works fine for
On Wed, 15 Aug 2007 23:54:43 +0900,
Tejun Heo <[EMAIL PROTECTED]> wrote:
> Alan Stern wrote:
> > I think we can simply remove the error message. There's no obvious
> > reason why sysfs_remove_bin_file() should complain about attempts to
> > remove a nonexistent file; sysfs_remove_file()
On Wed, Aug 15, 2007 at 03:45:08PM +0800, Dave Young wrote:
> >On 8/12/07, Randy Dunlap <[EMAIL PROTECTED]> wrote:
> > On Wed, 8 Aug 2007 07:39:33 + Dave Young wrote:
> >
> > > Hi,
> > > I have tried the "slow down printk" , and I have two questions.
> > >
> > > 1. why it depends the
Avi Kivity escreveu:
Glauber de Oliveira Costa wrote:
Andi Kleen escreveu:
On Wed, Aug 15, 2007 at 11:18:25AM -0300, Glauber de Oliveira Costa
wrote:
Didn't we agree this should be a pvops client?
-Andi
No. I exposed my reasoning, asked you back, but got no answer.
I'll do it again:
This
Kyle Moffett wrote:
> Basically any newly-created item in such a directory will get the
> permissions described by the "default:" entries in the ACL, and
> subdirectories will get a copy of said "default:" entries.
This would work well, although I would give write permissions to a group
so the
On Wed, 15 Aug 2007 16:03:39 +0800, gshan said:
> Bernd, Thanks for your reply. I don't think there are any hostile users
> on the system. So it's relatively of security. I didn't hear of coreadm
> tool before, Linux will become more powerful with coreadm.
Well, *right now* you don't have
Glauber de Oliveira Costa wrote:
Andi Kleen escreveu:
On Wed, Aug 15, 2007 at 11:18:25AM -0300, Glauber de Oliveira Costa
wrote:
Didn't we agree this should be a pvops client?
-Andi
No. I exposed my reasoning, asked you back, but got no answer.
I'll do it again:
This operations are just
Andi Kleen escreveu:
On Wed, Aug 15, 2007 at 11:18:25AM -0300, Glauber de Oliveira Costa wrote:
Didn't we agree this should be a pvops client?
-Andi
No. I exposed my reasoning, asked you back, but got no answer.
I'll do it again:
This operations are just manipulating bits, and are doing no
On Wednesday 15 August 2007 15:29:43 Arnd Bergmann wrote:
> On Wednesday 15 August 2007, Paul E. McKenney wrote:
>
> > ACCESS_ONCE() is indeed intended to be used when actually loading or
> > storing the variable. That said, I must admit that it is not clear to me
> > why you would want to add
Bodo Eggert wrote:
>> Ok, do you like this slightly better? It states the subsystem, the
>> function with the error, the block nr. in the case of a too-large block,
>> and the block device on which the error occurred.
>
> - how long is BDEVNAME_SIZE? Will it fit on the stack?
#define
Hi Linus,
Please pull from
git://git.kernel.org/pub/scm/linux/kernel/git/hskinnemoen/avr32-2.6.git
for-linus
to receive the following changes.
David Brownell (1):
[AVR32] leds-gpio for stk1000
Haavard Skinnemoen (4):
[AVR32] Wire up i2c-gpio on the ATNGW100 board
[AVR32]
On Wed, 15 Aug 2007, Florin Iucha wrote:
> [See my message to Alan]: It happened twice, within 15 minutes of
> boot+login, with 2.6.23-rc3-$whatever . I does not happen with
> 2.6.2[123](-rc*)? After the two incidents, I rebooted in 2.6.23-rc2 and
> it is working for an hour now.
It is not
On Wed, Aug 15, 2007 at 04:49:02PM +0200, Jiri Kosina wrote:
> On Wed, 15 Aug 2007, Florin Iucha wrote:
>
> > Today my USB keyboard stopped working in the middle of composing and
> > e-mail. I unplugged it and plugged it back, with no success. I
> > logged in remotely and found this lovely
Alan Stern wrote:
> I think we can simply remove the error message. There's no obvious
> reason why sysfs_remove_bin_file() should complain about attempts to
> remove a nonexistent file; sysfs_remove_file() doesn't.
>
> This patch will get rid of the annoying error messages. It won't do
>
On Wed, Aug 15, 2007 at 08:05:38PM +0530, Satyam Sharma wrote:
>
> > I don't know if this here is affected:
>
> Yes, I think it is. You're clearly expecting the read to actually happen
> when you call get_hpsb_generation(). It's clearly not a busy-loop, so
> cpu_relax() sounds pointless / wrong
On Wednesday 15 August 2007, Paul E. McKenney wrote:
> ACCESS_ONCE() is indeed intended to be used when actually loading or
> storing the variable. That said, I must admit that it is not clear to me
> why you would want to add an extra order() rather than ACCESS_ONCE()ing
> one or both of the
If during boot no ACPI 2.0 SLIT table is found we do not initialise
the NUMA node distance table, leaving all node distances as 0.
This causes IA-64 to fail the regression tests for libnuma. Also,
when we have a bad formatted table we will set all node distances
to 10. Both of these forms lose
On Wed, Aug 15, 2007 at 11:25:43AM -0300, Glauber de Oliveira Costa wrote:
> On 8/15/07, Andi Kleen <[EMAIL PROTECTED]> wrote:
> > > +#ifdef CONFIG_PARAVIRT
> > > +extern unsigned long *cpu_gdt_descr;
> >
> > No externs in .c files
> >
> > Normally they should be where the variable is defined
> >
On Wed, Aug 15, 2007 at 10:38:54AM -0400, Alan Stern wrote:
> This patch will get rid of the annoying error messages. It won't do
> anything about your keyboard's tendency to spontaneously stop working,
> alas.
My keyboard works fine for days, with kernels up to and including
2.6.23-rc2 . I
On Wed, 15 Aug 2007, Florin Iucha wrote:
> Today my USB keyboard stopped working in the middle of composing and
> e-mail. I unplugged it and plugged it back, with no success. I
> logged in remotely and found this lovely message:
The error message seems unrelated to your keyboard becoming dead.
On Wed, Aug 15, 2007 at 10:08:17AM -0400, Igor A. Nesterov wrote:
> So would it be true to say that the fix for -EEXIST problem still has
> not found its way to mainline kernel? I've been hit by this problem
> after switching to Fedora 7, and currently running on Fedora
> 2.6.21-1.3228 kernel
On Wed, Aug 15, 2007 at 11:18:25AM -0300, Glauber de Oliveira Costa wrote:
> > Didn't we agree this should be a pvops client?
> >
> > -Andi
> >
> No. I exposed my reasoning, asked you back, but got no answer.
> I'll do it again:
>
> This operations are just manipulating bits, and are doing no
>
David Miller wrote:
From: Sean Hefty <[EMAIL PROTECTED]>
Date: Thu, 09 Aug 2007 14:40:16 -0700
Steve Wise wrote:
Any more comments?
Does anyone have ideas on how to reserve the port space without using a
struct socket?
How about we just remove the RDMA stack altogether? I am not at all
[EMAIL PROTECTED] wrote:
> Add file pattern to MAINTAINER entry
>
> Signed-off-by: Joe Perches <[EMAIL PROTECTED]>
>
> diff --git a/MAINTAINERS b/MAINTAINERS
> index 9157b5d..1c014f1 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -1191,6 +1191,7 @@ M: [EMAIL PROTECTED]
> P: Joel
On Wed, 15 Aug 2007, Florin Iucha wrote:
> Today my USB keyboard stopped working in the middle of composing and
> e-mail. I unplugged it and plugged it back, with no success. I
> logged in remotely and found this lovely message:
>
> [ 1301.567351] usb 1-4: USB disconnect, address 3
> [
Sorry for the late commentary...as I looked this over, one thing popped
into my mind
> b) Make the 'clockid' immutable: it can only be set
>if 'ufd' is -1 -- that is, on the timerfd() call that
>first creates a timer.
timerfd() is looking increasingly like a multiplexor system call
> That is his second patch-set, and I do worry about the irq latency that
> that will introduce. It very much has the potential to ruin everything
> that cares about interactiveness or latency.
I proposed a way to avoid increasing interrupt latency
in a simple way.
-Andi
-
To unsubscribe from
On Aug 15, 2007, at 10:06:49, Jan Engelhardt wrote:
On Aug 15 2007 09:58, Kyle Moffett wrote:
Irrespective of whatever the standard says, EVERY platform and
compiler anybody makes nowadays has a NULL pointer value with all
bits clear. Theoretically the standard allows otherwise, but such
Quoting Lee Schermerhorn ([EMAIL PROTECTED]):
> On Tue, 2007-08-14 at 14:56 -0700, Christoph Lameter wrote:
> > On Tue, 14 Aug 2007, Lee Schermerhorn wrote:
> >
> > > > Ok then you did not have a NUMA system configured. So its okay for the
> > > > dummies to ignore the stuff. CONFIG_NODES_SHIFT
On Wed, Aug 15, 2007 at 07:17:29PM +0530, Satyam Sharma wrote:
> On Wed, 15 Aug 2007, Stefan Richter wrote:
> > Satyam Sharma wrote:
> > > On Wed, 15 Aug 2007, Stefan Richter wrote:
> > >> Doesn't "atomic WRT all processors" require volatility?
> > >
> > > No, it definitely doesn't. Why should
On 8/15/07, Andi Kleen <[EMAIL PROTECTED]> wrote:
> > +#ifdef CONFIG_PARAVIRT
> > +extern unsigned long *cpu_gdt_descr;
>
> No externs in .c files
>
> Normally they should be where the variable is defined
> anyways.
Given that this variable is defined in head.S, what do you propose?
AFAICT, this
Hi Stefan,
On Wed, 15 Aug 2007, Stefan Richter wrote:
> On 8/15/2007 10:18 AM, Heiko Carstens wrote:
> > On Wed, Aug 15, 2007 at 02:49:03PM +0800, Herbert Xu wrote:
> >> Chris Snook <[EMAIL PROTECTED]> wrote:
> >> >
> >> > Because atomic operations are generally used for synchronization, which
>
> Is the .globl really required here? I would think that the reference in
> the fixup section would be resolved with in the compiling of this object.
>
For the fixup yes, you are right. But I'm using this symbol in
paravirt.c now, to denote the native operation.
--
Glauber de Oliveira Costa.
Hi Russ,
in case you are still wondering about this...
There is a good explanation of the original reasoning here:
http://lists.opensuse.org/opensuse-bugs/2007-02/msg00149.html
And there are plans to remove the message here
http://www.uwsg.iu.edu/hypermail/linux/kernel/0707.3/2879.html
On Tue, Aug 14, 2007 at 11:25:33PM +0200, Adrian Bunk wrote:
> "extern inline" will have different semantics with gcc 4.3.
Thanks, I'll send this in.
BTW, I killed off CONFIG_MODE_TT yesterday.
Jeff
--
Work email - jdike at linux dot intel dot com
-
To
> Didn't we agree this should be a pvops client?
>
> -Andi
>
No. I exposed my reasoning, asked you back, but got no answer.
I'll do it again:
This operations are just manipulating bits, and are doing no
privileged operations at all. Nothing that can be paravirtualized, in
the proper sense.
Hi Thomas,
On 8/15/07, Thomas Renninger <[EMAIL PROTECTED]> wrote:
> +int pnp_port_alloc (struct pnp_resource_table *res)
> +{
> + int ret = 0, i;
> + if (res->allocated_ports == 0) {
> + res->port_resource = kmalloc(sizeof(struct resource)
> +
Raphaël Assénat wrote:
Mike Rapoport wrote:
Fix off-by-one in month calculations
Add delay for bus accesses to satisfy Tw > 500ns
*snip*
@@ -135,7 +140,7 @@ static int v3020_set_time(struct device *dev,
struct rtc_time *dt)
v3020_set_reg(chip, V3020_MINUTES, BIN2BCD(dt->tm_min));
--
On Wed, 15 Aug 2007, Glauber de Oliveira Costa wrote:
> @@ -566,10 +596,15 @@ retint_restore_args:
> restore_args:
> RESTORE_ARGS 0,8,0
> iret_label:
> +#ifdef CONFIG_PARAVIRT
> + INTERRUPT_RETURN
> +#endif
> +.globl do_iretq;
Is the .globl really required here? I would think
On Aug 15 2007 09:58, Kyle Moffett wrote:
>
> Irrespective of whatever the standard says, EVERY platform and
> compiler anybody makes nowadays has a NULL pointer value with all
> bits clear. Theoretically the standard allows otherwise, but such
> a decision would break so much code. Linux
Hi,
This is not a real feature, more a fix.
Without, PNP IO ports might not get considered. This mainly affects ACPI
system board devices with HID PNP0C02 (at least I saw this on my and
some other machines, but it may affect more...).
I expect this got introduced when resources were not handled
On Wed, 2007-08-15 at 04:13 -0400, Jeff Garzik wrote:
> Kristen Carlson Accardi wrote:
> > If a scsi_device supports async notification for media change, then
> > let user space know this capability exists by creating a new sysfs
> > entry "media_change_notify", which will be 1 if it is supported,
On Aug 15, 2007, at 06:20:27, Jan Engelhardt wrote:
On Aug 15 2007 11:58, Rene Herman wrote:
NULL is not 0 though.
It is. Its representation isn't guaranteed to be all-bits-zero,
He said the null _pointer_ isn't guaranteed to be all-bits zero.
And it isn't. Read the standard or the faq.
On Wed, 2007-08-15 at 16:15 +0200, Andi Kleen wrote:
> Peter Zijlstra <[EMAIL PROTECTED]> writes:
> >
> > Christoph's suggestion to set min_free_kbytes to 20% is ridiculous - nor
> > does it solve all deadlocks :-(
>
> A minimum enforced reclaimable non dirty threshold wouldn't be
> that
On Aug 15, 2007, at 09:39:44, Rene Herman wrote:
On 08/15/2007 03:33 PM, Satyam Sharma wrote:
[ git info --maintainer ]
I'd really _love_ a tool that does all that what you've proposed
above! But why does it have to be "git-info" or anything in the
git(7) suite for that matter? This
On Aug 15, 2007, at 09:30:21, Lennart Sorensen wrote:
On Wed, Aug 15, 2007 at 09:02:37AM -0400, Michael Tharp wrote:
Personally, what I'd like to see is a better way of dealing with
propagation of ownership. Currently, in order to allow
"collaboration" directories where a directory tree is
On 8/15/2007 10:18 AM, Heiko Carstens wrote:
> On Wed, Aug 15, 2007 at 02:49:03PM +0800, Herbert Xu wrote:
>> Chris Snook <[EMAIL PROTECTED]> wrote:
>> >
>> > Because atomic operations are generally used for synchronization, which
>> > requires
>> > volatile behavior. Most such codepaths
Currently block device size calculated regardless its
bd_block_size. This may result attempt to write outside
block device if i_size not aligned to bdev->bd_block_size
and result in EIO.
TEST_CASE_BEGIN
# fdisk -l /dev/sdc
Disk /dev/sdc: 36.7 GB, 36703918080 bytes
255 heads, 63
* Satyam Sharma | 2007-08-15 18:32:10 [+0530]:
>On Wed, 15 Aug 2007, Herbert Xu wrote:
>
>> Andi Kleen <[EMAIL PROTECTED]> wrote:
>> >> My config with march=pentium-m and gcc (GCC) 4.1.2 (Gentoo 4.1.2):
>> >> textdata bss dec hex filename
>> >> 3434150 249176 176128 3859454
On 08/15/2007 03:33 PM, Satyam Sharma wrote:
[ git info --maintainer ]
I'd really _love_ a tool that does all that what you've proposed above!
But why does it have to be "git-info" or anything in the git(7) suite for
that matter? This sounds like a job for a different specialised tool,
along
On Tue, 2007-08-14 at 14:56 -0700, Christoph Lameter wrote:
> On Tue, 14 Aug 2007, Lee Schermerhorn wrote:
>
> > > Ok then you did not have a NUMA system configured. So its okay for the
> > > dummies to ignore the stuff. CONFIG_NODES_SHIFT is a constant and does
> > > not
> > > change. The
Today my USB keyboard stopped working in the middle of composing and
e-mail. I unplugged it and plugged it back, with no success. I
logged in remotely and found this lovely message:
[ 1301.567351] usb 1-4: USB disconnect, address 3
[ 1301.567356] usb 1-4.2: USB disconnect, address 5
[
Mike Rapoport wrote:
Fix off-by-one in month calculations
Add delay for bus accesses to satisfy Tw > 500ns
*snip*
@@ -135,7 +140,7 @@ static int v3020_set_time(struct device *dev, struct
rtc_time *dt)
v3020_set_reg(chip, V3020_MINUTES, BIN2BCD(dt->tm_min));
v3020_set_reg(chip,
On Wed, 15 Aug 2007, Stefan Richter wrote:
> Satyam Sharma wrote:
> > On Wed, 15 Aug 2007, Stefan Richter wrote:
> >> Doesn't "atomic WRT all processors" require volatility?
> >
> > No, it definitely doesn't. Why should it?
> >
> > "Atomic w.r.t. all processors" is just your normal, simple
On Wed, Aug 15, 2007 at 09:02:37AM -0400, Michael Tharp wrote:
> This jumped out at me right away. In such a system, an attacker with
> write permissions on a "sticky" directory like /tmp could probe for
> others' files by attempting to create them and recording all cases where
> permission was
Paul E. McKenney wrote:
On Tue, Aug 14, 2007 at 03:34:25PM +1000, Nick Piggin wrote:
Maybe it is the safe way to go, but it does obscure cases where there
is a real need for barriers.
I prefer burying barriers into other primitives.
When they should naturally be there, eg. locking or the
Hi Rene,
On Wed, 15 Aug 2007, Rene Herman wrote:
> It mostly is just about that it seems. However, this would not also allow the
> other information currently in the MAINTAINERS file to be queried in similar
> ways.
>
> Git could grow a generic file meta data implementation through the use of
Peter Zijlstra <[EMAIL PROTECTED]> writes:
>
> Christoph's suggestion to set min_free_kbytes to 20% is ridiculous - nor
> does it solve all deadlocks :-(
A minimum enforced reclaimable non dirty threshold wouldn't be
that ridiculous though. So the memory could be used, just not
for dirty data.
Michael Neuling wrote:
> b663a79c191508f27cd885224b592a878c0ba0f6 incorrectly removed a comma
> from a printf statement. This causes corruption in the output printing
> or a seg fault.
>
> Signed-off-by: Michael Neuling <[EMAIL PROTECTED]>
> ---
> Documentation/accounting/getdelays.c |2 +-
alan wrote:
> Imagine the fun you will have trying to write a file name and being told
> you cannot write it for some unknown reason. Unbeknownst to you, there
> is a file there, but it is not owned by you, thus invisible.
This jumped out at me right away. In such a system, an attacker with
I wrote:
> static inline void A(atomic_t *a)
> {
> int b = atomic_read(a);
> if (b)
> do_something_time_consuming();
> }
>
> static inline void B(atomic_t *a)
> {
> int b = atomic_read(a);
> if (b)
> do_something_more();
> }
>
> static void
On Wed, 2007-08-15 at 14:22 +0200, Nick Piggin wrote:
> On Tue, Aug 14, 2007 at 07:21:03AM -0700, Christoph Lameter wrote:
> > The following patchset implements recursive reclaim. Recursive reclaim
> > is necessary if we run out of memory in the writeout patch from reclaim.
> >
> > This is f.e.
> +#ifdef CONFIG_PARAVIRT
> +extern unsigned long *cpu_gdt_descr;
No externs in .c files
Normally they should be where the variable is defined
anyways.
-Andi
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo
Satyam Sharma wrote:
> On Wed, 15 Aug 2007, Stefan Richter wrote:
>> Doesn't "atomic WRT all processors" require volatility?
>
> No, it definitely doesn't. Why should it?
>
> "Atomic w.r.t. all processors" is just your normal, simple "atomicity"
> for SMP systems (ensure that that object is
> Can you please add a comment, that this line must stay in a single line
> for the above reason? I would expect that the next who does some code
> clean up will break it again.
Then we would need to add it to all macros essentially. That wouldn't
be economical.
-Andi
-
To unsubscribe from this
* Tore Anderson
> I can confirm that this patch solves my problem without any side
> effects (as far as I can tell).
I'm sorry I have to retract this statement. When I did some changes
on my storage array, it generated RSCNs and therefore I/O briefly
failed, causing timeouts and path
> +#ifdef CONFIG_X86_VSMP
> +static inline int raw_irqs_disabled_flags(unsigned long flags)
> +{
> + return !(flags & X86_EFLAGS_IF) || (flags & X86_EFLAGS_AC);
> +}
> +
> +#else
> static inline int raw_irqs_disabled_flags(unsigned long flags)
> {
> return !(flags & X86_EFLAGS_IF);
>
This is finally, the patch we were all looking for. This
patch adds a paravirt.h header with the definition of paravirt_ops
struct. Also, it defines a bunch of inline functions that will
replace, or hook, the other calls. Every one of those functions
adds an entry in the parainstructions section
This patch add paravirtualization hooks in the arch initialization
process. paravirt_arch_setup() lets the guest issue any specific
initialization routine
Also, there is memory_setup(), so guests can handle it their way.
[ updates from v1
* Don't use a separate ebda pv hook (Jeremy/Andi)
This patch turns the irq_flags and halt routines into the
native versions.
[ updates from v1
Move raw_irqs_disabled_flags outside of the PARAVIRT ifdef to
avoid increasing the mess, suggested by Andi Kleen
]
Signed-off-by: Glauber de Oliveira Costa <[EMAIL PROTECTED]>
Signed-off-by: Steven
This patch introduces apply_paravirt(), a function that shall
be called by i386/alternative.c to apply replacements to
paravirt_functions. It is defined to an do-nothing function
if paravirt is not enabled.
Signed-off-by: Glauber de Oliveira Costa <[EMAIL PROTECTED]>
Signed-off-by: Steven Rostedt
This is hopefully the last iteration of the pvops64 patch.
>From the last version, we have only one change, which is
>include/asm-x86_64/processor.h: There were still one survivor in raw asm.
Also, git screwed me up for some reason, and the 25th patch was missing the new
files, paravirt.{c,h}.
This patch add provisions for time related functions so they
can be later replaced by paravirt versions.
it basically encloses {g,s}et_wallclock inside the
already existent functions update_persistent_clock and
read_persistent_clock, and defines {s,g}et_wallclock
to the core of such functions.
under paravirt, read cr2 cannot be issued directly anymore.
So wrap it in a macro, defined to the operation itself in case
paravirt is off, but to something else if we have paravirt
in the game
Signed-off-by: Glauber de Oliveira Costa <[EMAIL PROTECTED]>
Signed-off-by: Steven Rostedt <[EMAIL
With paravirualization, hypervisors needs to handle the gdt,
that was right to this point only used at very early
inialization code. Hypervisors are commonly modules, so make
it an export
[ updates from v1
* make it an EXPORT_SYMBOL_GPL.
Suggested by Arjan van de Ven
]
Signed-off-by:
This patch replaces syscall_init by x86_64_syscall_init.
The former will be later replaced by a paravirt replacement
in case paravirt is on
Signed-off-by: Glauber de Oliveira Costa <[EMAIL PROTECTED]>
Signed-off-by: Steven Rostedt <[EMAIL PROTECTED]>
---
arch/x86_64/kernel/setup64.c |8
This patch introduces a new macro/function that informs a paravirt
guest when its page table is not more in use, and can be released.
In case we're not paravirt, just do nothing.
Signed-off-by: Glauber de Oliveira Costa <[EMAIL PROTECTED]>
Signed-off-by: Steven Rostedt <[EMAIL PROTECTED]>
---
With paravirt on, we cannot issue operations like swapgs, sysretq,
iretq, cli, sti. So they have to be changed into macros, that will
be later properly replaced for the paravirt case.
The sysretq is a little bit more complicated, and is replaced
by a sequence of three instructions. It is
This function/macro will allow a paravirt guest to be notified we changed
the current task cr3, and act upon it. It's up to them
Signed-off-by: Glauber de Oliveira Costa <[EMAIL PROTECTED]>
Signed-off-by: Steven Rostedt <[EMAIL PROTECTED]>
---
include/asm-x86_64/mmu_context.h | 17
This patch turns the page operations (set and make a page table)
into native_ versions. The operations itself will be later
overriden by paravirt.
Signed-off-by: Glauber de Oliveira Costa <[EMAIL PROTECTED]>
Signed-off-by: Steven Rostedt <[EMAIL PROTECTED]>
---
include/asm-x86_64/page.h | 36
This patch turns the basic descriptor handling into native_
functions. It is basically write_idt, load_idt, write_gdt,
load_gdt, set_ldt, store_tr, load_tls, and the ones
for updating a single entry.
In the process of doing that, we change the definition of
load_LDT_nolock, and caller sites have
Besides not elegant, it is now even forbidden, since it can
break paravirtualized guests. load_cr3 should call write_cr3()
instead.
Signed-off-by: Glauber de Oliveira Costa <[EMAIL PROTECTED]>
Signed-off-by: Steven Rostedt <[EMAIL PROTECTED]>
---
include/asm-x86_64/mmu_context.h |2 +-
1
This patch turns the set_p{te,md,ud,gd} functions into their
native_ versions. There is no need to patch any caller.
Also, it adds pte_update() and pte_update_defer() calls whenever
we modify a page table entry. This last part was coded to match
i386 as close as possible.
Pieces of the header
This patch turns makes the basic operations in msr.h out of native
ones. Those operations are: rdmsr, wrmsr, rdtsc, rdtscp, rdpmc, and
cpuid. After they are turned into functions, some call sites need
casts, and so we provide them.
There is also a fixup needed in the functions located in the
Export math_state_restore symbol, so it can be used for hypervisors.
They are commonly loaded as modules.
Signed-off-by: Glauber de Oliveira Costa <[EMAIL PROTECTED]>
Signed-off-by: Steven Rostedt <[EMAIL PROTECTED]>
---
arch/x86_64/kernel/traps.c |1 +
1 files changed, 1 insertions(+), 0
When paravirtualization is disabled, the kernel is always
running at ring 0. So report it in the appropriate macro
Signed-off-by: Glauber de Oliveira Costa <[EMAIL PROTECTED]>
Signed-off-by: Steven Rostedt <[EMAIL PROTECTED]>
---
include/asm-x86_64/segment.h |4
1 files changed, 4
The interrupt initialization routine becomes native_init_IRQ and will
be overriden later in case paravirt is on.
[ updates from v1
* After a talk with Jeremy Fitzhardinge, it turned out that making the
interrupt vector global was not a good idea. So it is removed in this
patch
]
This patch switches the cli and sti instructions into macros.
In this header, they're just defined to the instructions they
refer to. Later on, when paravirt is defined, they will be
defined to something with paravirt abilities.
Signed-off-by: Glauber de Oliveira Costa <[EMAIL PROTECTED]>
Time for the apic handling functions to get their native counterparts.
Also, put the native hook for the boot clocks functions in the apic.h header
Signed-off-by: Glauber de Oliveira Costa <[EMAIL PROTECTED]>
Signed-off-by: Steven Rostedt <[EMAIL PROTECTED]>
---
arch/x86_64/kernel/apic.c|
This patch turns the flush_tlb routines into native versions.
In case paravirt is not defined, the natives are defined into
the actually used ones. flush_tlb_others() goes in smp.c, unless
smp is not in the game
Signed-off-by: Glauber de Oliveira Costa <[EMAIL PROTECTED]>
Signed-off-by: Steven
This patch adds native hooks for debugreg handling functions,
and for the native load_rsp0 function. The later also have its
call sites patched.
[ updates from v2
* there were still a raw reference to cr4 missing
]
Signed-off-by: Glauber de Oliveira Costa <[EMAIL PROTECTED]>
Signed-off-by:
This patch adds the native hook for the functions in system.h
They are the read/write_crX, clts and wbinvd. The later, also
gets its call sites patched.
Signed-off-by: Glauber de Oliveira Costa <[EMAIL PROTECTED]>
Signed-off-by: Steven Rostedt <[EMAIL PROTECTED]>
---
arch/x86_64/kernel/tce.c
Later on, the paravirt_ops patch will deference the vm_area_struct
in asm/pgtable.h. It means this define must be after the struct
definition
Signed-off-by: Glauber de Oliveira Costa <[EMAIL PROTECTED]>
Signed-off-by: Steven Rostedt <[EMAIL PROTECTED]>
---
include/linux/mm.h | 14
On Wed, 15 Aug 2007, Herbert Xu wrote:
> Andi Kleen <[EMAIL PROTECTED]> wrote:
> >> My config with march=pentium-m and gcc (GCC) 4.1.2 (Gentoo 4.1.2):
> >> textdata bss dec hex filename
> >> 3434150 249176 176128 3859454 3ae3fe atomic_normal/vmlinux
> >> 3435308 249176
Hi,
I noticed that a bad CD of mine makes DMA disabled:
hda: selected mode 0x44
hda: cdrom_decode_status: status=0x51 { DriveReady SeekComplete Error }
hda: cdrom_decode_status: error=0x40 { LastFailedSense=0x04 }
ide: failed opcode was: unknown
hda: cdrom_decode_status: status=0x51 {
On Wed, Aug 15, 2007 at 02:59:20PM +0200, Andi Kleen wrote:
> On Wed, Aug 15, 2007 at 12:37:49PM +0100, Ralf Baechle wrote:
> > On Tue, Aug 14, 2007 at 02:14:41AM +0200, Andi Kleen wrote:
> >
> > > meth is only used on SGI O2s which are not that slow and unlikely
> > > to work in tree anyways.
>
301 - 400 of 984 matches
Mail list logo
