search for: unmasked

patch revision history ---------------------- v1: Initial patch to handle this issue involving changing the hypercall interface v2:Totally handled inside hypervisor. v3:Change some logics of handling msi-x pending unmask operations. v4:Some changes related to coding style according to Andrew Cooper''s comments From 51c5b7f1f9c8f319da8adf021b39e18fbd3bf314 Mon Sep 17 00:00:00 2001 From:

patch revision history ---------------------- v1: Initial patch to handle this issue involving changing the hypercall interface v2:Totally handled inside hypervisor. v3:Change some logics of handling msi-x pending unmask operations. v4:Some changes related to coding style according to Andrew Cooper''s comments v5:Some changes according to Jan''s comments, including a) remove

Aah.. Sorry typo. systemctl unmask samba-ad-dc (umask / unmask ) systemctl enable samba-ad-dc systemctl start samba-ad-dc Im very buzy, so slow in responce atm, but if a service fails to upgrade and starts it gets masked. Unmasking is needed then. To make sure its all enable i also run extra enable. > -----Oorspronkelijk bericht----- > Van: Stefan G. Weichinger [mailto:lists at

On 07/18/2019 11:32 AM, Rowland penny via samba wrote: > Hurrah and this part is easy ;-) > > You are starting the wrong binary, you need to start 'samba-ad-dc' , > you may have to unmask it though. Yippee, that worked!? I was able to unmask (systemctl unmask samba-ad-dc) and samba started.? wbinfo --ping-dc returns the new DC!? Also get correct groups and users with wbinfo

CPUIDLE: Avoid remnant LAPIC timer intr while force hpetbroadcast LAPIC will stop during C3, and resume to work after exit from C3. Considering below case: The LAPIC timer was programmed to expire after 1000us, but CPU enter C3 after 100us and exit C3 at 9xxus. 0us: reprogram_timer(1000us) 100us: entry C3, LAPIC timer stop 9xxus: exit C3 due to unexpected event, LAPIC timer continue running

In <Xen In seterface Manual>, chapter 5 Event Channels, they say that:"Event Notifications can be masked by setting a flag; this is equivalent to disabling interrupts and can be used to ensure atomicity of certain operation in the guest kernel". My question is : I know that we can use ''xc_evtchn_unmask(xcehandle, port)'' to unmask an event channel , but I can not

...i_desc); + orig = readl(virt); - val &= ~PCI_MSIX_VECTOR_BITMASK; - val |= orig & PCI_MSIX_VECTOR_BITMASK; + + /* + * Do not allow guest to modify MSI-X control bit if it is masked + * by Xen. We''ll only handle the case where Xen thinks that + * bit is unmasked, but hardware has silently masked the bit + * (in case of SR-IOV VF reset, etc). On the other hand, if Xen + * thinks that the bit is masked, but it''s really not, + * we log a warning. + */ + if ( msi_desc->msi_attrib.masked ) + { + if ( !(orig & PCI_M...

> -----Oorspronkelijk bericht----- > Van: samba [mailto:samba-bounces at lists.samba.org] Namens > Stefan G. Weichinger via samba > Verzonden: vrijdag 6 maart 2020 10:41 > Aan: samba at lists.samba.org > Onderwerp: Re: [Samba] DCs from 4.10.x to 4.11.x > > Am 06.03.20 um 10:11 schrieb L.P.H. van Belle via samba: > > After upgrade indexing is done as far i know.

On 07/18/2019 11:04 AM, Rowland penny via samba wrote: > I have never had to deal with a W2K AD server, but from my > understanding W2K didn't have the DNS records in AD, so I wondered if > yours didn't either. I am running out of ideas now. > > Have you tried Tim's patch ? > > Just in case you don't know how to apply the patch, it is pretty > simple, it

...arted. If so walk away, have a >> three course meal and go to the cinema, hopefully when you get back, it >> will have finished reindexing your database. > > kind of, yes. short: works now > > longer: reinstalled samba, found samba-ad-dc.service masked (why? who?) > ... unmasked it and decided to restart. Works now. > > thanks for now. I will wait with the second DC, one or two days. I have to add that the customer had issues while DC1 was reindexing or whatever ...

Am 05.03.20 um 17:39 schrieb Rowland penny via samba: > On 05/03/2020 16:31, Stefan G. Weichinger via samba wrote: >> Am 05.03.20 um 16:09 schrieb Rowland penny via samba: >> >>> It took nearly 5 hours in my case and during that time, only the samba >>> binary was running, no smbd or winbind. >> Why 5 hours? Thousands of users? > No, just my small test

I tried the Louis Van Belle's Debian backport of Samba 4.4.5 and I observed one obscure behaviour. I am running it on Debian 8.6.0.  I just run Samba as a NT4 PDC and do simple file sharing.  When my server is rebooted, my PCs cannot see the domain.  Everything seems fine when I checked the status of the Samba using "/etc/init.d/samba status".  However once I restart Samba

Hi, I have a problem while loading the "siar" program in R. When I am loading siar, system does not load convexhull. On the screen I have seen such writings. The following object(s) are masked from ‘package:spatstat’: convexhull How can I load the convexhull, how can I unmask from this package? I will be appreciated if you give advice about this. Best Sukran

What you want to know is.. ## For a standalone server/Member server. systemctl stop samba-ad-dc samba systemctl disable samba-ad-dc samba systemctl mask samba-ad-dc samba systemctl unmask smbd winbind nmbd systemctl enable smbd winbind nmbd systemctl start smbd winbind nmbd ## For an AD-DC setup. systemctl stop smbd nmbd winbind systemctl disable smbd nmbd winbind systemctl mask smbd nmbd

...rized: > > for (...) { > A > if (...) { > B > } else { > C > } > D > } > > Assuming there's a bunch of code in B and a bunch in C, then > we have four bunches of code and three mask conditions - > A and D are unmasked, B is masked, and C is masked with the > inverse mask value. This code could easily have more if > branches, nested loops, early exits, and so on, but the main > idea is that there are blocks of instructions grouped together > under the same mask, cross-block optimization opportunities...

On Mon, May 27, 2019 at 12:43:41PM +0200, Miroslav Geisselreiter (mg at intar.cz) wrote: > Hi Jobst, > > you can use latest samba package from CentOS 7 - there is no problem with NT > style domains support (ie. it supports NT style domains). We use servers > with CentOS 6 and CentOS 7 both with NT style domains. Phew! Thank you, this is great news! I had huge trouble to get the

Am 12.07.2016 um 21:35 schrieb Rowland penny: > On 12/07/16 20:25, Achim Gottinger wrote: >> Just backported 4.4.5 from debian sid to jessie. samba.service is >> masked there. If running as an fileserver the services are started >> via smbd.service,nmbd.service, winbind.service. >> There is an samba-ad-dc script which is masked by default. >> To get the ad-dc up

Just backported 4.4.5 from debian sid to jessie. samba.service is masked there. If running as an fileserver the services are started via smbd.service,nmbd.service, winbind.service. There is an samba-ad-dc script which is masked by default. To get the ad-dc up and running with systemd one has to unmask samba-ad-dc.service and mask smbd.service,nmbd.service, winbind.service. This is the

...all generating i64 in the scalar function signature: // Type 1 typedef _Complex int S; // Type 2 typedef struct x{ int a; int b; } S; // Type 3 typedef uint64_t S; S foo(S a, S b) { return ...; } On AArch64, the correspondent vector function signature in the three cases would be (for 2-lane unmasked vectorization): // Type 1: <4 x int> vectorized_foo(<4 x int>, <4 x int>) // Type 2: %a = type struct {I 32, i32} <2 x %a* > vectorized_foo(<2 x %a*> , <2 x %a*>) // Type 3: <2 x i64> vectorized_foo(<2 x i64>, <2 x i64) To make sure that th...

...a function by function > basis. This RFC approaches the same issue differently, but it's still > there -- in terms of this RFC, operations on scalable vectors depend > on `vscale`, which is "not necessarily [constant] across functions". > That implies, for example, that an unmasked <scalable 4 x i32> load or > store (which accesses vscale * 16 bytes of memory) can't generally be > moved from one function to another unless it's somehow ensured that > both functions will have the same vscale. For that matter, the same > restriction applies to calls to...