search for: hstop

...you have an explicit solution? My problems is that I am trying to figure out during what conditions one may find 5 significant parameters in a logistic regression with only 21 bad and 28 outcomes (this appears in a published article) and I would like to have ?my.glm<-try(glm(outcome~ald + fat+ hstop + btun + time, data=DF, family=binomial)) to indicate if warnings (convergence / probabilities equal to 0/1) occurs (see attempt to code below if my explanation is terse). Best regards, Fredrik Nilsson ------------------------------------------------------------------------------ Fredrik Nilsson...

...rescue clauses to catch all exceptions AND NOT EXIT so that the SCM could still send the stop message, so that the threads would be cleaned up and etc. * ErrorStopService removed because it was abused - called when it didn''t make sense. Instead, I explicitly put in error handling and set hStopEvent or set service status appropriately. Probably could still be better. * Waiting for hThread to exit AFTER closing hStopEvent (which might be waiting on hStopEvent) * the state SHOULD == RUNNING when service_main starts (I had a problem where it was 0). * EventHookHash was a global variable...

...more hacks and just >> have everyone switch to that. > > There are a couple of problems with VIRTIO_F_IOMMU_PLATFORM: > > 1. It doesn't exist for legacy devices, which are all we have on the > platform in question. > > 2. It's not documented in the virtio sp^H^HSTOP PRESS. I see you applied > my patch ;). Thanks. > > In which case, for non-legacy devices we should definitely be using > VIRTIO_F_IOMMU_PLATFORM, but since this platform hasn't yet moved to the > world of flying cars, could we unconditionally set the DMA ops on ARM > for l...

...more hacks and just >> have everyone switch to that. > > There are a couple of problems with VIRTIO_F_IOMMU_PLATFORM: > > 1. It doesn't exist for legacy devices, which are all we have on the > platform in question. > > 2. It's not documented in the virtio sp^H^HSTOP PRESS. I see you applied > my patch ;). Thanks. > > In which case, for non-legacy devices we should definitely be using > VIRTIO_F_IOMMU_PLATFORM, but since this platform hasn't yet moved to the > world of flying cars, could we unconditionally set the DMA ops on ARM > for l...

On Tue, Jan 10, 2017 at 05:51:18PM +0000, Robin Murphy wrote: > From: Will Deacon <will.deacon at arm.com> > > Booting Linux on an ARM fastmodel containing an SMMU emulation results > in an unexpected I/O page fault from the legacy virtio-blk PCI device: > > [ 1.211721] arm-smmu-v3 2b400000.smmu: event 0x10 received: > [ 1.211800] arm-smmu-v3 2b400000.smmu:

On Tue, Jan 10, 2017 at 05:51:18PM +0000, Robin Murphy wrote: > From: Will Deacon <will.deacon at arm.com> > > Booting Linux on an ARM fastmodel containing an SMMU emulation results > in an unexpected I/O page fault from the legacy virtio-blk PCI device: > > [ 1.211721] arm-smmu-v3 2b400000.smmu: event 0x10 received: > [ 1.211800] arm-smmu-v3 2b400000.smmu:

...e hacks and just > > have everyone switch to that. > > There are a couple of problems with VIRTIO_F_IOMMU_PLATFORM: > > 1. It doesn't exist for legacy devices, which are all we have on the > platform in question. > > 2. It's not documented in the virtio sp^H^HSTOP PRESS. I see you applied > my patch ;). Thanks. > > In which case, for non-legacy devices we should definitely be using > VIRTIO_F_IOMMU_PLATFORM, but since this platform hasn't yet moved to the > world of flying cars, could we unconditionally set the DMA ops on ARM > for...

...e hacks and just > > have everyone switch to that. > > There are a couple of problems with VIRTIO_F_IOMMU_PLATFORM: > > 1. It doesn't exist for legacy devices, which are all we have on the > platform in question. > > 2. It's not documented in the virtio sp^H^HSTOP PRESS. I see you applied > my patch ;). Thanks. > > In which case, for non-legacy devices we should definitely be using > VIRTIO_F_IOMMU_PLATFORM, but since this platform hasn't yet moved to the > world of flying cars, could we unconditionally set the DMA ops on ARM > for...

...; > > > There are a couple of problems with VIRTIO_F_IOMMU_PLATFORM: > > > > > > 1. It doesn't exist for legacy devices, which are all we have on the > > > platform in question. > > > > > > 2. It's not documented in the virtio sp^H^HSTOP PRESS. I see you applied > > > my patch ;). Thanks. > > > > > > In which case, for non-legacy devices we should definitely be using > > > VIRTIO_F_IOMMU_PLATFORM, but since this platform hasn't yet moved to the > > > world of flying cars, could w...

...; > > > There are a couple of problems with VIRTIO_F_IOMMU_PLATFORM: > > > > > > 1. It doesn't exist for legacy devices, which are all we have on the > > > platform in question. > > > > > > 2. It's not documented in the virtio sp^H^HSTOP PRESS. I see you applied > > > my patch ;). Thanks. > > > > > > In which case, for non-legacy devices we should definitely be using > > > VIRTIO_F_IOMMU_PLATFORM, but since this platform hasn't yet moved to the > > > world of flying cars, could w...

...; I'd rather we avoided need for more hacks and just > have everyone switch to that. There are a couple of problems with VIRTIO_F_IOMMU_PLATFORM: 1. It doesn't exist for legacy devices, which are all we have on the platform in question. 2. It's not documented in the virtio sp^H^HSTOP PRESS. I see you applied my patch ;). Thanks. In which case, for non-legacy devices we should definitely be using VIRTIO_F_IOMMU_PLATFORM, but since this platform hasn't yet moved to the world of flying cars, could we unconditionally set the DMA ops on ARM for legacy devices? The alternativ...

...ryone switch to that. > > > > There are a couple of problems with VIRTIO_F_IOMMU_PLATFORM: > > > > 1. It doesn't exist for legacy devices, which are all we have on the > > platform in question. > > > > 2. It's not documented in the virtio sp^H^HSTOP PRESS. I see you applied > > my patch ;). Thanks. > > > > In which case, for non-legacy devices we should definitely be using > > VIRTIO_F_IOMMU_PLATFORM, but since this platform hasn't yet moved to the > > world of flying cars, could we unconditionally set the...

...re a couple of problems with VIRTIO_F_IOMMU_PLATFORM: > > > > > > > > 1. It doesn't exist for legacy devices, which are all we have on the > > > > platform in question. > > > > > > > > 2. It's not documented in the virtio sp^H^HSTOP PRESS. I see you applied > > > > my patch ;). Thanks. > > > > > > > > In which case, for non-legacy devices we should definitely be using > > > > VIRTIO_F_IOMMU_PLATFORM, but since this platform hasn't yet moved to the > > > > worl...

...ith VIRTIO_F_IOMMU_PLATFORM: > > > > > > > > > > 1. It doesn't exist for legacy devices, which are all we have on the > > > > > platform in question. > > > > > > > > > > 2. It's not documented in the virtio sp^H^HSTOP PRESS. I see you applied > > > > > my patch ;). Thanks. > > > > > > > > > > In which case, for non-legacy devices we should definitely be using > > > > > VIRTIO_F_IOMMU_PLATFORM, but since this platform hasn't yet moved to the >...

...ith VIRTIO_F_IOMMU_PLATFORM: > > > > > > > > > > 1. It doesn't exist for legacy devices, which are all we have on the > > > > > platform in question. > > > > > > > > > > 2. It's not documented in the virtio sp^H^HSTOP PRESS. I see you applied > > > > > my patch ;). Thanks. > > > > > > > > > > In which case, for non-legacy devices we should definitely be using > > > > > VIRTIO_F_IOMMU_PLATFORM, but since this platform hasn't yet moved to the >...