Displaying 8 results from an estimated 8 matches for "acessses".
Did you mean:
acesses
2006 Dec 07
0
Rmpi help
Hi team,
I am beginning on R and I try to install Rmpi library and I have problems, I have installed LAM-MPI on Rocks;
[rcnavarro at hpc-cip ~]$ laminfo
LAM/MPI: 7.1.1
Prefix: /opt/lam/gnu
Architecture: x86_64-unknown-linux-gnu
Configured by: root
Configured on: Wed Oct 19 18:12:25 EDT 2005
Configure host: rocks-156.sdsc.edu
Memory
2015 Feb 25
2
[PATCH 2/2] nouveau: Do not add most bo's to the global bo list.
So you're saying a compiler can optimize:
>
> - statement with memory access
> - read memory barrier
> - statement with memory access
>
> To drop the second statement? I would worry about your definition of
> memory barrier then..
>
This is tricky, but I think you're mixing up the general case with the
actual code you have. In general, you are pointing to this
2006 Aug 21
7
RFC: xencomm in common
Hi,
xencomm is the ppc infrastructure to do hypercalls with guest physical
addresses instead of virtual address.
Because ia64 should also use physicall address, I think it''s better to re-use
the ppc code and to put into common code.
I''d propose to submit this patch is every part is OK (ie no NAK).
This patch creates include/xen/xencomm_access.h which is to be included by
2011 Dec 13
12
[PATCH 0 of 4 V2] oxenstored fixes -- fixes recent pvops kernel hang
Currently PVHVM Linux guests after ddacf5ef684a "xen/pv-on-hvm kexec:
add xs_reset_watches to shutdown watches from old kernel" hang when
run against oxenstored because it does not handle the unknown
XS_RESET_WATCHES operation and does not reply.
The symptom of this issue is a hang during boot at this point:
cpu 1 spinlock event irq 70
CPU 1 irqstacks, hard=dec94000
2015 Feb 25
0
[PATCH 2/2] nouveau: Do not add most bo's to the global bo list.
pthread_mutex_lock had *better* imply a compiler barrier across which
code can't be moved... which is very different from the printf case
where it might have done it due to register pressure or who knows
what.
If code like
x = *a;
pthread_mutex_lock or unlock or __memory_barrier()
y = *a;
doesn't cause a to get loaded twice, then the compiler's in serious
trouble. Basically
2015 Mar 09
4
[LLVMdev] Counting load and stores of variables
Hi all,
I’m working on my thesis in which I need to count the number of memory access (i.e. load and stores) of each variable of program. how can I do that? these are some approaches came to my mind :
I need to know during the execution of the program how many load and store instructions are executed on a specific variable, hence simply counting static load and store instructions doesn’t help.
2015 Feb 25
3
[PATCH 2/2] nouveau: Do not add most bo's to the global bo list.
On Wed, Feb 25, 2015 at 9:07 AM, Maarten Lankhorst <
maarten.lankhorst at ubuntu.com> wrote:
> Op 25-02-15 om 16:04 schreef Patrick Baggett:
> > On Wed, Feb 25, 2015 at 8:59 AM, Maarten Lankhorst <
> > maarten.lankhorst at ubuntu.com> wrote:
> >
> >> Op 25-02-15 om 15:11 schreef Emil Velikov:
> >>> On 24 February 2015 at 09:01, Maarten
2011 Jul 20
12
Re: Re: XAPI on debian - sr-create issue
You''re right scout the last line. Out looks like xapi is waiting on tapdisk to plug a key into xenstore. Perhaps a udev rule problem? Perhaps someone who knows more about tapdisk than I well be able to diagnose this tomorrow.
Mike
Sent from Samsung tablet
Sébastien RICCIO <sr@swisscenter.com> wrote:
Of course, here it is attached.
Last line seems interesting. However tapdisk2