search for: empted

Displaying 20 results from an estimated 49 matches for "empted".

Did you mean: tempted
2005 Jan 17
4
DIDs anywhere but here?
Are there affordable DIDs (preferably IAX) available anywhere outside the US? I want to use it to meet ICANN requirements for providing a valid phone number, yet pre-empting some of the telemarketing calls my domain registrations generate. (Yes, I asked a similar question about 900# availability before). I'd prefer to have a number somewhere outside the NANP, preferably an asian country.
2005 Sep 15
2
ppc questions
Chris Mauritz wrote: > > The 32bit PPC release is for the older G3/G4 macs, no? I've got a > pile of unused G4 400-800mhz powermacs just sitting around The ppc32 distro will work on any NewWorld G3, G4 based machine ( and 32bit ibm power, like the older rs6k's ) - it _also_ works fine on the MacMini and G4 Xserve's. With some common sense tweaks, a G4 450Mhz is a very
2019 May 27
3
[RFC PATCH 5/6] x86/mm/tlb: Flush remote and local TLBs concurrently
..._t, __pv_tlb_mask); -static void kvm_flush_tlb_others(const struct cpumask *cpumask, +static void kvm_flush_tlb_multi(const struct cpumask *cpumask, const struct flush_tlb_info *info) { u8 state; @@ -594,6 +594,9 @@ static void kvm_flush_tlb_others(const s * queue flush_on_enter for pre-empted vCPUs */ for_each_cpu(cpu, flushmask) { + if (cpu == smp_processor_id()) + continue; + src = &per_cpu(steal_time, cpu); state = READ_ONCE(src->preempted); if ((state & KVM_VCPU_PREEMPTED)) { @@ -603,7 +606,7 @@ static void kvm_flush_tlb_others(const s } } - native...
2019 May 27
3
[RFC PATCH 5/6] x86/mm/tlb: Flush remote and local TLBs concurrently
..._t, __pv_tlb_mask); -static void kvm_flush_tlb_others(const struct cpumask *cpumask, +static void kvm_flush_tlb_multi(const struct cpumask *cpumask, const struct flush_tlb_info *info) { u8 state; @@ -594,6 +594,9 @@ static void kvm_flush_tlb_others(const s * queue flush_on_enter for pre-empted vCPUs */ for_each_cpu(cpu, flushmask) { + if (cpu == smp_processor_id()) + continue; + src = &per_cpu(steal_time, cpu); state = READ_ONCE(src->preempted); if ((state & KVM_VCPU_PREEMPTED)) { @@ -603,7 +606,7 @@ static void kvm_flush_tlb_others(const s } } - native...
2016 Nov 04
2
CentOS-7 x86_64 AMIs and consistent network device naming
Hello, Re: https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7-Beta/html/7.3_Release_Notes/bug_fixes_general_updates.html Are there any upcoming plans for turning off the use of legacy interface names in the next official CentOS 7.x AMI? Currently, both the official RHEL 7.3 GA AMI and the latest available official CentOS-7 x86_64 AMI use legacy interface names via either:
2006 Apr 06
2
Two XGL questions
I know this list is meant for discussion of compiz specifically, but .... 1) I sometimes see compiz spit out "Could not bind pixmap to texture" messages, even though it _appears_ to be working fine. I randomly guess that this is due to me running out of video memory (iirc I have 64mb of vram). Is that possibly a problem? I think Vista and OS X manually manage video
2007 Aug 23
5
[PATCH] Fix preemptible lazy mode bug
...ntly sent off a fix for lazy vmalloc faults which can happen under = paravirt when lazy mode is enabled. Unfortunately, I jumped the gun a = bit on fixing this. I neglected to notice that since the new call to = flush the MMU update queue is called from the page fault handler, it can = be pre-empted. Both VMI and Xen use per-cpu variables to track lazy = mode state, as all previous calls to set, disable, or flush lazy mode = happened from a non-preemptable state. I have no idea how to convincingly produce the problem, as generating a = kernel pre-emption at the required point is, um, diff...
2007 Aug 23
5
[PATCH] Fix preemptible lazy mode bug
...ntly sent off a fix for lazy vmalloc faults which can happen under = paravirt when lazy mode is enabled. Unfortunately, I jumped the gun a = bit on fixing this. I neglected to notice that since the new call to = flush the MMU update queue is called from the page fault handler, it can = be pre-empted. Both VMI and Xen use per-cpu variables to track lazy = mode state, as all previous calls to set, disable, or flush lazy mode = happened from a non-preemptable state. I have no idea how to convincingly produce the problem, as generating a = kernel pre-emption at the required point is, um, diff...
2019 May 27
1
[RFC PATCH 5/6] x86/mm/tlb: Flush remote and local TLBs concurrently
...t struct cpumask *cpumask, > > +static void kvm_flush_tlb_multi(const struct cpumask *cpumask, > > const struct flush_tlb_info *info) > > { > > u8 state; > > @@ -594,6 +594,9 @@ static void kvm_flush_tlb_others(const s > > * queue flush_on_enter for pre-empted vCPUs > > */ > > for_each_cpu(cpu, flushmask) { > > + if (cpu == smp_processor_id()) > > + continue; > > + > > Even this would be just an optimization; the vCPU you're running on > cannot be preempted. You can just change others to multi. Yeah,...
2005 Sep 13
1
Floating-point arithmetic
Hi Folks, A recent exchange on the 'octave' list led to the following paper being cited, which I had not met before: What Every Computer Scientist Should Know About Floating-Point Arithmetic, by David Goldberg, originally published in the March, 1991 issue of Computing Surveys. PDF and HTML versions are widely available on the web (see Google), e.g. at
2009 Mar 25
2
[LLVMdev] pragmas
Pre-empting Chris's inevitable response: don't add intrinsics! I really like the 'disappearing function calls' idea. Chris suggested practically the same thing for a previous question about adding BigInt support. Anthony, whichever route you take in the end, please consider documenting your 'code adventure' on the wiki so others can learn from your experience. Justing
2016 Feb 11
2
[RFC] Error handling in LLVM libraries.
Hi All, Now that this thread has accumulated some feedback, I thought I'd try to summarize my thoughts on error handling in LLVM, and why I think this proposal is worth adopting: (1) Failure to check an error *is* a programmatic error, and our error system should reflect this. This makes it easy to spot mistakes in our error handling and correct them. (2) Error returns should describe all
2005 Mar 20
2
Using locator() to digitise
Hi Folks, I'm contemplating using locator() to digitise external graphics. To set context, I would be using X11 display on Linux. To pre-empt the obvious comment: I've found on the R site the suggestion to use the 'pixmap' package. I've tried this, and it works; but it involves building a big R object (the internal pixmap representation), and this chokes my somewhat puny
2009 Mar 25
0
[LLVMdev] pragmas
Thanks for the quick responses. "disappearing function calls" is by far the preferred way for me, as I want my pass to work with standard LLVM and not a hacked version that supports extra pragmas, or intrinsics. I am just new to LLVM and wanted to make sure that there isn't already a mechanism for passing meta-data between the user and the optimizer. I am planning to
2007 Jun 12
6
ensure => latest forcing recompile?
I''m running puppet from svn - build 2537. I''ve got a functional configuration and am testing it on a couple of development machines prior to moving it into production. I noticed today that the machines are taking ~300 seconds to process their configurations, so i watched a run and saw that it''s recompiling all of the Packages every single time. The only thing
2003 Jul 24
3
R won't connect to the internet on Linux!
OK, I really am struggling with this one! Forgive me if I am being stupid.... I am running R 1.7.1 on Suse Linux 8.1. I connect to the internet through a proxy so I have: IAHC-LINUX03:~ # echo $http_proxy wwwcache.bbsrc.ac.uk:8080 IAHC-LINUX03:~ # echo $HTTP_PROXY wwwcache.bbsrc.ac.uk:8080 just in case ;-) SO, i go into R and I get: >
2003 Jun 16
4
POP daemon
What would be a good POP daemon to use? I know there are a few in the mail ports. Are they any good? What I mean by good is 'secure as possible' (is there really such thing as being totally secure / invulnerable?) Cheers
2019 May 27
0
[RFC PATCH 5/6] x86/mm/tlb: Flush remote and local TLBs concurrently
...void kvm_flush_tlb_others(const struct cpumask *cpumask, > +static void kvm_flush_tlb_multi(const struct cpumask *cpumask, > const struct flush_tlb_info *info) > { > u8 state; > @@ -594,6 +594,9 @@ static void kvm_flush_tlb_others(const s > * queue flush_on_enter for pre-empted vCPUs > */ > for_each_cpu(cpu, flushmask) { > + if (cpu == smp_processor_id()) > + continue; > + Even this would be just an optimization; the vCPU you're running on cannot be preempted. You can just change others to multi. Paolo > src = &per_cpu(steal_time,...
2016 Nov 04
0
CentOS-7 x86_64 AMIs and consistent network device naming
On 04/11/16 11:18, Jinesh Choksi wrote: > Hello, > > Re: > https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7-Beta/html/7.3_Release_Notes/bug_fixes_general_updates.html > > Are there any upcoming plans for turning off the use of legacy interface > names in the next official CentOS 7.x AMI? > > Currently, both the official RHEL 7.3 GA AMI and the
2017 Nov 14
0
IMAP connections with ".eml" in the username - bot attack.
James Brown writes: > We are seeing lots of IMAP login attempts like this: > > dovecot[363]: imap-login: Disconnected (auth failed, 1 attempts in 6 secs): user=<xcentrex5fxnewx5fxyorkx5fxquotex5fxisx5fxreadyx2dxx2dx426453.eml>, method=PLAIN, rip=197.255.60.118, > dovecot[363]: imap-login: Disconnected (auth failed, 1 attempts in 6 secs):