search for: longman

Displaying 20 results from an estimated 467 matches for "longman".

2010 Aug 01
3
Longman iBT 2.0 Toefl
Hello. Can anyone please take a second to help me out with this problem? I try to run Longman iBT 2.0 Toefl with the last version of Wine / Lubuntu / FGLRX (video driver for ATI HD 4330 ) / Java. I have the last version of all these... As you can see, the program runs but some items are not displayed or wrong displayed. Moving the pointer or moving the window can make the image better or wo...
2004 Sep 29
1
[Fwd: Re: Newbie]
-------------- next part -------------- An embedded message was scrubbed... From: Giuseppe Taroni <horsehorse@libero.it> Subject: Re: [Wine] Newbie Date: Wed, 29 Sep 2004 14:00:07 +0200 Size: 5903 Url: http://www.winehq.org/pipermail/wine-users/attachments/20040929/aa9b6754/attachment.mht
2017 Feb 13
5
[PATCH v2] x86/paravirt: Don't make vcpu_is_preempted() a callee-save function
...point). > >> Maybe: > >> > >> movsql %edi, %rax; > >> movq __per_cpu_offset(,%rax,8), %rax; > >> cmpb $0, %[offset](%rax); > >> setne %al; > >> > >> ? > > Yes, that looks good to me. > > > > Cheers, > > Longman > > > Sorry, I am going to take it back. The displacement or offset can only > be up to 32-bit. So we will still need to use at least one more > register, I think. I don't think that would be a problem, I very much doubt we declare more than 4G worth of per-cpu variables in the...
2017 Feb 13
5
[PATCH v2] x86/paravirt: Don't make vcpu_is_preempted() a callee-save function
...point). > >> Maybe: > >> > >> movsql %edi, %rax; > >> movq __per_cpu_offset(,%rax,8), %rax; > >> cmpb $0, %[offset](%rax); > >> setne %al; > >> > >> ? > > Yes, that looks good to me. > > > > Cheers, > > Longman > > > Sorry, I am going to take it back. The displacement or offset can only > be up to 32-bit. So we will still need to use at least one more > register, I think. I don't think that would be a problem, I very much doubt we declare more than 4G worth of per-cpu variables in the...
2014 Apr 23
2
[PATCH v9 05/19] qspinlock: Optimize for smaller NR_CPUS
...ink I was confused :-) Make the 1 _Q_LOCKED_VAL though, as >>>> that's the proper constant to use. >>> Everyone gets confused once in a while:-) I have plenty of that myself. >>> >>> I will change 1 to _Q_LOCKED_VAL as suggested. >>> >>> -Longman >> >> The attached patch file contains the additional changes that I had >> made to qspinlock.c file so far. Please let me know if you or others >> have any additional feedbacks or changes that will need to go to the >> next version of the patch series. >> >&g...
2014 Apr 23
2
[PATCH v9 05/19] qspinlock: Optimize for smaller NR_CPUS
...ink I was confused :-) Make the 1 _Q_LOCKED_VAL though, as >>>> that's the proper constant to use. >>> Everyone gets confused once in a while:-) I have plenty of that myself. >>> >>> I will change 1 to _Q_LOCKED_VAL as suggested. >>> >>> -Longman >> >> The attached patch file contains the additional changes that I had >> made to qspinlock.c file so far. Please let me know if you or others >> have any additional feedbacks or changes that will need to go to the >> next version of the patch series. >> >&g...
2014 Apr 23
1
[PATCH v9 05/19] qspinlock: Optimize for smaller NR_CPUS
...though, as >>>>>> that's the proper constant to use. >>>>> Everyone gets confused once in a while:-) I have plenty of that myself. >>>>> >>>>> I will change 1 to _Q_LOCKED_VAL as suggested. >>>>> >>>>> -Longman >>>> The attached patch file contains the additional changes that I had >>>> made to qspinlock.c file so far. Please let me know if you or others >>>> have any additional feedbacks or changes that will need to go to the >>>> next version of the patch...
2014 Apr 23
1
[PATCH v9 05/19] qspinlock: Optimize for smaller NR_CPUS
...though, as >>>>>> that's the proper constant to use. >>>>> Everyone gets confused once in a while:-) I have plenty of that myself. >>>>> >>>>> I will change 1 to _Q_LOCKED_VAL as suggested. >>>>> >>>>> -Longman >>>> The attached patch file contains the additional changes that I had >>>> made to qspinlock.c file so far. Please let me know if you or others >>>> have any additional feedbacks or changes that will need to go to the >>>> next version of the patch...
2017 Feb 13
2
[PATCH v2] x86/paravirt: Don't make vcpu_is_preempted() a callee-save function
...nonsense, but I'm not sure I see how to do that (then again, >> this asm foo isn't my strongest point). > Maybe: > > movsql %edi, %rax; > movq __per_cpu_offset(,%rax,8), %rax; > cmpb $0, %[offset](%rax); > setne %al; > > ? Yes, that looks good to me. Cheers, Longman
2017 Feb 13
2
[PATCH v2] x86/paravirt: Don't make vcpu_is_preempted() a callee-save function
...nonsense, but I'm not sure I see how to do that (then again, >> this asm foo isn't my strongest point). > Maybe: > > movsql %edi, %rax; > movq __per_cpu_offset(,%rax,8), %rax; > cmpb $0, %[offset](%rax); > setne %al; > > ? Yes, that looks good to me. Cheers, Longman
2014 Apr 23
2
[PATCH v9 05/19] qspinlock: Optimize for smaller NR_CPUS
...nfused by your notation. >> Nah, I think I was confused :-) Make the 1 _Q_LOCKED_VAL though, as >> that's the proper constant to use. > > Everyone gets confused once in a while:-) I have plenty of that myself. > > I will change 1 to _Q_LOCKED_VAL as suggested. > > -Longman The attached patch file contains the additional changes that I had made to qspinlock.c file so far. Please let me know if you or others have any additional feedbacks or changes that will need to go to the next version of the patch series. I am going to take vacation starting from tomorrow and...
2014 Apr 23
2
[PATCH v9 05/19] qspinlock: Optimize for smaller NR_CPUS
...nfused by your notation. >> Nah, I think I was confused :-) Make the 1 _Q_LOCKED_VAL though, as >> that's the proper constant to use. > > Everyone gets confused once in a while:-) I have plenty of that myself. > > I will change 1 to _Q_LOCKED_VAL as suggested. > > -Longman The attached patch file contains the additional changes that I had made to qspinlock.c file so far. Please let me know if you or others have any additional feedbacks or changes that will need to go to the next version of the patch series. I am going to take vacation starting from tomorrow and...
2002 Mar 02
0
Longman dictionary installer debugging
Hi! I'm trying to install the Longman Dictionary of Contemporary English (which I have got with the book with the same name). I'm running: the latest wine release (20020228) Redhat 7.2 gcc 2.96-98 fake windows dir (altough I have tried it with a win98 install a month ago) The installer is an installshild with win16 libs. When I...
2019 Mar 25
2
[PATCH] x86/paravirt: Guard against invalid cpu # in pv_vcpu_is_preempted()
...] Hardware name: Red Hat KVM, BIOS 0.5.1 01/01/2011 [ 2.533321] RIP: 0010:__raw_callee_save___kvm_vcpu_is_preempted+0x0/0x20 To guard against this kind of kernel panic, check is added to pv_vcpu_is_preempted() to make sure that no invalid cpu number will be used. Signed-off-by: Waiman Long <longman at redhat.com> --- arch/x86/include/asm/paravirt.h | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/arch/x86/include/asm/paravirt.h b/arch/x86/include/asm/paravirt.h index c25c38a05c1c..4cfb465dcde4 100644 --- a/arch/x86/include/asm/paravirt.h +++ b/arch/x86/include/asm/paravirt.h @@ -...
2019 Mar 25
2
[PATCH] x86/paravirt: Guard against invalid cpu # in pv_vcpu_is_preempted()
...] Hardware name: Red Hat KVM, BIOS 0.5.1 01/01/2011 [ 2.533321] RIP: 0010:__raw_callee_save___kvm_vcpu_is_preempted+0x0/0x20 To guard against this kind of kernel panic, check is added to pv_vcpu_is_preempted() to make sure that no invalid cpu number will be used. Signed-off-by: Waiman Long <longman at redhat.com> --- arch/x86/include/asm/paravirt.h | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/arch/x86/include/asm/paravirt.h b/arch/x86/include/asm/paravirt.h index c25c38a05c1c..4cfb465dcde4 100644 --- a/arch/x86/include/asm/paravirt.h +++ b/arch/x86/include/asm/paravirt.h @@ -...
2019 Mar 25
2
[PATCH] x86/paravirt: Guard against invalid cpu # in pv_vcpu_is_preempted()
...[ 2.533321] RIP: 0010:__raw_callee_save___kvm_vcpu_is_preempted+0x0/0x20 >> >> To guard against this kind of kernel panic, check is added to >> pv_vcpu_is_preempted() to make sure that no invalid cpu number will >> be used. >> >> Signed-off-by: Waiman Long <longman at redhat.com> >> --- >> arch/x86/include/asm/paravirt.h | 6 ++++++ >> 1 file changed, 6 insertions(+) >> >> diff --git a/arch/x86/include/asm/paravirt.h b/arch/x86/include/asm/paravirt.h >> index c25c38a05c1c..4cfb465dcde4 100644 >> --- a/arch/x86/inc...
2019 Mar 25
2
[PATCH] x86/paravirt: Guard against invalid cpu # in pv_vcpu_is_preempted()
...[ 2.533321] RIP: 0010:__raw_callee_save___kvm_vcpu_is_preempted+0x0/0x20 >> >> To guard against this kind of kernel panic, check is added to >> pv_vcpu_is_preempted() to make sure that no invalid cpu number will >> be used. >> >> Signed-off-by: Waiman Long <longman at redhat.com> >> --- >> arch/x86/include/asm/paravirt.h | 6 ++++++ >> 1 file changed, 6 insertions(+) >> >> diff --git a/arch/x86/include/asm/paravirt.h b/arch/x86/include/asm/paravirt.h >> index c25c38a05c1c..4cfb465dcde4 100644 >> --- a/arch/x86/inc...
2020 Jul 08
1
[PATCH v3 0/6] powerpc: queued spinlocks and rwlocks
On Tue, Jul 07, 2020 at 11:33:45PM -0400, Waiman Long wrote: > From 5d7941a498935fb225b2c7a3108cbf590114c3db Mon Sep 17 00:00:00 2001 > From: Waiman Long <longman at redhat.com> > Date: Tue, 7 Jul 2020 22:29:16 -0400 > Subject: [PATCH 2/9] locking/pvqspinlock: Introduce > CONFIG_PARAVIRT_QSPINLOCKS_LITE > > Add a new PARAVIRT_QSPINLOCKS_LITE config option that allows > architectures to use the PV qspinlock code without the need to use...
2014 Apr 18
2
[PATCH v9 05/19] qspinlock: Optimize for smaller NR_CPUS
On Fri, Apr 18, 2014 at 01:52:50PM -0400, Waiman Long wrote: > I am confused by your notation. Nah, I think I was confused :-) Make the 1 _Q_LOCKED_VAL though, as that's the proper constant to use.
2014 Apr 18
2
[PATCH v9 05/19] qspinlock: Optimize for smaller NR_CPUS
On Fri, Apr 18, 2014 at 01:52:50PM -0400, Waiman Long wrote: > I am confused by your notation. Nah, I think I was confused :-) Make the 1 _Q_LOCKED_VAL though, as that's the proper constant to use.