ralphc> I didn't try calling barrier() so I don't know the answer.
ralphc> When power is restored, I can try it. My guess is that
ralphc> it's a timing issue and not a code reordering issue.
Hmm, then we really better understand what's going on, because
otherwise you're just going to have trouble again if someone makes a
CPU with a faster mfence instruction...
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
- References:
- [PATCH 53 of 53] ipath - add memory barrier when waiting for writes
- From: "Bryan O'Sullivan" <[email protected]>
- Re: [PATCH 53 of 53] ipath - add memory barrier when waiting for writes
- From: Roland Dreier <[email protected]>
- Re: [PATCH 53 of 53] ipath - add memory barrier when waiting for writes
- From: "Bryan O'Sullivan" <[email protected]>
- Re: [PATCH 53 of 53] ipath - add memory barrier when waiting for writes
- From: [email protected]
- Re: [PATCH 53 of 53] ipath - add memory barrier when waiting for writes
- From: Roland Dreier <[email protected]>
- Re: [PATCH 53 of 53] ipath - add memory barrier when waiting for writes
- From: [email protected]
- Re: [openib-general] Re: [PATCH 53 of 53] ipath - add memory barrier when waiting for writes
- From: Roland Dreier <[email protected]>
- Re: [openib-general] Re: [PATCH 53 of 53] ipath - add memory barrier when waiting for writes
- From: [email protected]
- [PATCH 53 of 53] ipath - add memory barrier when waiting for writes
- Prev by Date: Re: Regression seen for patch "sched:dont decrease idle sleep avg"
- Next by Date: Re: [RFT] major libata update
- Previous by thread: Re: [openib-general] Re: [PATCH 53 of 53] ipath - add memory barrier when waiting for writes
- Next by thread: [PATCH 51 of 53] ipath - fix reporting of vendor ID and a few other trivial bits
- Index(es):
 |