Displaying 20 results from an estimated 23 matches for "03.07.19".
2019 Jul 03
2
PTR Records in AD
Hello you all,
I have a general question. How do you guys handle the PTR record in AD
if the workstations update their own records? The A record is no problem
as this contains the name and is onyl updated by the corresponding
machine. However, the PTR record could be tried to update by a different
machine if that IP has been passed to a different machine by DHCP. With
windows AD with scavenging of
2019 Jul 03
2
`samba-tool dbcheck --cross-ncs --fix` fails: governsID already exists as an attributeId or governsId
On 03.07.19 17:19, Rowland penny via samba wrote:
>> All these object classes were tests we did? years ago, and which have
>> been "deleted" (I don't even remember by what mechanism) for almost as
>> long. No object should still be using any of these, and on graz-dc-sem
>> that's true.
> I would love to know how you deleted something from the schema, it
2019 Jul 04
2
`samba-tool dbcheck --cross-ncs --fix` fails: governsID already exists as an attributeId or governsId
On 03.07.19 18:04, Rowland penny via samba wrote:
>>>> How do I get rid of these bogus Schema entries, and how do I fix the
>>>> user account?
>>> I do not think you can remove anything from the schema, but I believe
>>> you can deactivate schema objects, try reading this:
>>>
>>>
2019 Jul 03
2
[PATCH v2 4/9] x86/mm/tlb: Flush remote and local TLBs concurrently
On 03.07.19 01:51, Nadav Amit wrote:
> To improve TLB shootdown performance, flush the remote and local TLBs
> concurrently. Introduce flush_tlb_multi() that does so. Introduce
> paravirtual versions of flush_tlb_multi() for KVM, Xen and hyper-v (Xen
> and hyper-v are only compile-tested).
>
> While the updated smp infrastructure is capable of running a function on
> a single
2019 Jul 03
2
[PATCH v2 4/9] x86/mm/tlb: Flush remote and local TLBs concurrently
On 03.07.19 01:51, Nadav Amit wrote:
> To improve TLB shootdown performance, flush the remote and local TLBs
> concurrently. Introduce flush_tlb_multi() that does so. Introduce
> paravirtual versions of flush_tlb_multi() for KVM, Xen and hyper-v (Xen
> and hyper-v are only compile-tested).
>
> While the updated smp infrastructure is capable of running a function on
> a single
2019 Jul 03
3
optimisation issue in an llvm IR pass
Hi Craig,
On 03.07.19 17:33, Craig Topper wrote:
> Don't the CreateICmp calls return a Value* with an i1 type? But then
> they are added to an i8 type? Not sure that works.
I had that initially:
auto cf = IRB.CreateICmpULT(Incr, ConstantInt::get(Int8Ty, 1));
auto carry = IRB.CreateZExt(cf, Int8Ty);
Incr = IRB.CreateAdd(Incr, carry);
it makes no difference to the generated assembly
2019 Jul 03
1
[Xen-devel] [PATCH v2 4/9] x86/mm/tlb: Flush remote and local TLBs concurrently
On 03/07/2019 18:02, Nadav Amit wrote:
>> On Jul 3, 2019, at 7:04 AM, Juergen Gross <jgross at suse.com> wrote:
>>
>> On 03.07.19 01:51, Nadav Amit wrote:
>>> To improve TLB shootdown performance, flush the remote and local TLBs
>>> concurrently. Introduce flush_tlb_multi() that does so. Introduce
>>> paravirtual versions of flush_tlb_multi() for
2019 Jul 04
2
[PATCH 0/5] Unmappable DRM client buffers for fbdev emulation
Hi
Am 03.07.19 um 21:27 schrieb Noralf Tr?nnes:
>
>
> Den 03.07.2019 10.32, skrev Thomas Zimmermann:
>> DRM client buffers are permanently mapped throughout their lifetime. This
>> prevents us from using generic framebuffer emulation for devices with
>> small dedicated video memory, such as ast or mgag200. With fb buffers
>> permanently mapped, such devices
2019 Jul 04
2
[PATCH 0/5] Unmappable DRM client buffers for fbdev emulation
Hi
Am 03.07.19 um 21:27 schrieb Noralf Tr?nnes:
>
>
> Den 03.07.2019 10.32, skrev Thomas Zimmermann:
>> DRM client buffers are permanently mapped throughout their lifetime. This
>> prevents us from using generic framebuffer emulation for devices with
>> small dedicated video memory, such as ast or mgag200. With fb buffers
>> permanently mapped, such devices
2019 Jul 03
0
PTR Records in AD
Hi Christian,
normally I never do a reverse lookup for clients only for server and
then the reverse lookup is static. If a customer want's it I do it this way:
https://wiki.samba.org/index.php/Configure_DHCP_to_update_DNS_records_with_BIND9
Stefan
Am 03.07.19 um 11:41 schrieb Christian Naumer via samba:
> Hello you all,
> I have a general question. How do you guys handle the PTR
2019 Jul 03
0
`samba-tool dbcheck --cross-ncs --fix` fails: governsID already exists as an attributeId or governsId
On 03/07/2019 16:26, Sven Schwedas via samba wrote:
> On 03.07.19 17:19, Rowland penny via samba wrote:
>>> All these object classes were tests we did? years ago, and which have
>>> been "deleted" (I don't even remember by what mechanism) for almost as
>>> long. No object should still be using any of these, and on graz-dc-sem
>>> that's
2019 Jul 04
0
`samba-tool dbcheck --cross-ncs --fix` fails: governsID already exists as an attributeId or governsId
On 04/07/2019 14:45, Sven Schwedas via samba wrote:
> On 03.07.19 18:04, Rowland penny via samba wrote:
>>>>> How do I get rid of these bogus Schema entries, and how do I fix the
>>>>> user account?
>>>> I do not think you can remove anything from the schema, but I believe
>>>> you can deactivate schema objects, try reading this:
2019 Jul 03
0
[PATCH v2 4/9] x86/mm/tlb: Flush remote and local TLBs concurrently
> On Jul 3, 2019, at 7:04 AM, Juergen Gross <jgross at suse.com> wrote:
>
> On 03.07.19 01:51, Nadav Amit wrote:
>> To improve TLB shootdown performance, flush the remote and local TLBs
>> concurrently. Introduce flush_tlb_multi() that does so. Introduce
>> paravirtual versions of flush_tlb_multi() for KVM, Xen and hyper-v (Xen
>> and hyper-v are only
2019 Jul 04
0
[PATCH 0/5] Unmappable DRM client buffers for fbdev emulation
Den 04.07.2019 13.10, skrev Thomas Zimmermann:
> Hi
>
> Am 04.07.19 um 12:18 schrieb Noralf Tr?nnes:
>>
>>
>> Den 04.07.2019 09.43, skrev Thomas Zimmermann:
>>> Hi
>>>
>>> Am 03.07.19 um 21:27 schrieb Noralf Tr?nnes:
>>>>
>>>>
>>>> Den 03.07.2019 10.32, skrev Thomas Zimmermann:
>>>>> DRM
2019 Jul 04
2
[PATCH 0/5] Unmappable DRM client buffers for fbdev emulation
Hi
Am 04.07.19 um 12:18 schrieb Noralf Tr?nnes:
>
>
> Den 04.07.2019 09.43, skrev Thomas Zimmermann:
>> Hi
>>
>> Am 03.07.19 um 21:27 schrieb Noralf Tr?nnes:
>>>
>>>
>>> Den 03.07.2019 10.32, skrev Thomas Zimmermann:
>>>> DRM client buffers are permanently mapped throughout their lifetime. This
>>>> prevents us from
2019 Jul 04
2
[PATCH 0/5] Unmappable DRM client buffers for fbdev emulation
Hi
Am 04.07.19 um 12:18 schrieb Noralf Tr?nnes:
>
>
> Den 04.07.2019 09.43, skrev Thomas Zimmermann:
>> Hi
>>
>> Am 03.07.19 um 21:27 schrieb Noralf Tr?nnes:
>>>
>>>
>>> Den 03.07.2019 10.32, skrev Thomas Zimmermann:
>>>> DRM client buffers are permanently mapped throughout their lifetime. This
>>>> prevents us from
2019 Jul 04
0
[PATCH 0/5] Unmappable DRM client buffers for fbdev emulation
Den 04.07.2019 09.43, skrev Thomas Zimmermann:
> Hi
>
> Am 03.07.19 um 21:27 schrieb Noralf Tr?nnes:
>>
>>
>> Den 03.07.2019 10.32, skrev Thomas Zimmermann:
>>> DRM client buffers are permanently mapped throughout their lifetime. This
>>> prevents us from using generic framebuffer emulation for devices with
>>> small dedicated video memory,
2019 Jul 03
2
`samba-tool dbcheck --cross-ncs --fix` fails: governsID already exists as an attributeId or governsId
It's amazing how long Samba just keeps running even when apparently
everything's broken.
In preparation of finally upgrading our DCs to 41.0, I ran dbcheck on
all of them, resulting in:
graz-dc-sem:
> Checking 3861 objects
> Error: governsID CN=ucsUser,CN=Schema,CN=Configuration,DC=ad,DC=tao,DC=at on 1.3.6.1.4.1.19414.3.2.2 already exists as an attributeId or governsId
> Error:
2019 Jul 03
1
[PATCH 1/5] drm/client: Support unmapping of DRM client buffers
Den 03.07.2019 10.32, skrev Thomas Zimmermann:
> DRM clients, such as the fbdev emulation, have their buffer objects
> mapped by default. Mapping a buffer implicitly prevents its relocation.
> Hence, the buffer may permanently consume video memory while it's
> allocated. This is a problem for drivers of low-memory devices, such as
> ast, mgag200 or older framebuffer hardware,
2019 Jul 03
2
optimisation issue in an llvm IR pass
Hello,
I have an optimisation issue in an llvm IR pass - the issue being that
unnecessary instructions are generated in the final assembly (with -O3).
I want to create the following assembly snippet:
mov dl,BYTE PTR [rsi+rdi*1]
add dl,0x1
adc dl,0x0
mov BYTE PTR [rsi+rdi*1],dl
however what is created is (variant #1):
mov dl,BYTE PTR [rsi+rdx*1]
add dl,0x1
cmp